PyVO
PyVO is a package providing access to remote data and services of the Virtual observatory (VO) using Python.
Its development was launched by the NSF/NASA-funded Virtual Astronomical Observatory (VAO) project (formerly under the name VAOpy) as part of its initiative to bring VO capabilities to desktop.
PyVO main goal is to allow astronomers and tool developers to access data and services from remote archives and other web resources. It takes advantage of VO standards to give access to thousands of catalogs, data archives, information services, and analysis tools. It also takes advantage of the general capabilities of Astopy (and numpy), and so a secondary goal is to provide a development platform for prototypes for functionalities that are under development and not yet accepted as a VO standard.
Source code can be found on GitHub
Installation and Requirements
Releases of PyVO are available from PyPI thus, it and its prerequisites can be most easily installed using pip:
pip install pyvo
Releases are also conda packaged and available on the conda-forge channel.
To install from source use pip:
pip install .[all]
Using the developer version of PyVO in testing
We recommend and encourage testing against the development version of PyVO in CI, both for dependent libraries and notebook providers. As PyVO is a pure Python library, this can be done as easily as pip installing the developer version from GitHub:
pip install git+https://github.com/astropy/pyvo.git#egg=pyvo
An example for setting up development version testing for a library as a GitHub Actions Workflow can be found in astroquery.
Examples
Many instructive examples can be found in the PyVO Documentation. Additional examples can be found in the examples directory.
Unit Tests
PyVO uses the Astropy framework for unit tests which is built into the setup script. To run the tests, type:
pip install .[test] pytest
This will run all unit tests that do not require a network connection. To run all tests, including those that access the network, add the –remote-data option:
pytest –remote-data
5 maintainers
Metadata
5 maintainers
Release files for pyvo 1.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyvo-1.10.0.tar.gz | 2.2 MB | Without provenance | Details for pyvo-1.10.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyvo-1.10.0-py3-none-any.whl | Python 3 | none | any | Details for pyvo-1.10.0-py3-none-any.whl |
Total release size: 3.3 MB
Release files / pyvo-1.10.0.tar.gz
| Download URL | pyvo-1.10.0.tar.gz |
|---|---|
| Size | 2.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b70048d114b8dc827588e571ba84bebb6e7eb6d5b9121a17cb307ad2fe9081e
|
|
BLAKE2b-256 checksum How to use checksums |
43af56a4a6f5fbb276cb94a57cb245987207390e5378998602aa5493ebd5c625
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.9
|
Release files / pyvo-1.10.0-py3-none-any.whl
| Download URL | pyvo-1.10.0-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a53d636635b53dc38d846b766593c181d9a4dfcaf6b88ec5e2d05a46d9aac15
|
|
BLAKE2b-256 checksum How to use checksums |
a21b0677a4534f8bf0271c8e671f7fdb95a26dfe4c93336589ef9d6eef9e6dc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.9
|
Security for pyvo 1.10.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
