Skip to content

BUG: Copying a TAPService has side affects #755

@emellega

Description

@emellega

When copying a TAPService instance with an auth session we get some kind of validation as a side affect. Here's a minimal python script to reproduce the issue:

import pyvo, copy
auth = pyvo.auth.authsession.AuthSession()
tap = pyvo.dal.TAPService('https://sky.esa.int/esasky-tap/tap', session=auth)
copy.deepcopy(tap)

It produces this warning:

WARNING: W19: ?:?:?: W19: TAP Capabilities must not have an ivo-id other than ivo://ivoa.net/std/TAP [pyvo.io.vosi.tapregext]
WARNING:astropy:W19: ?:?:?: W19: TAP Capabilities must not have an ivo-id other than ivo://ivoa.net/std/TAP

This issue was noticed when caching requests in astroquery. This PR introduces a temporary workaround in astroquery.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions