Support for astrometry timeseries analysis.
1 maintainer
Metadata
1 maintainer
Release files for pystrometry 0.6.1
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 | |
|---|---|---|---|---|
| pystrometry-0.6.1.tar.gz | 226.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pystrometry-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 319.4 kB
Release files / pystrometry-0.6.1.tar.gz
| Download URL | pystrometry-0.6.1.tar.gz |
|---|---|
| Size | 226.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
adc9b5a7284492d0ce4307307b3366ba6578c9a2cd9f45dd46a198e42de7ea02
|
|
BLAKE2b-256 checksum How to use checksums |
aa44ee79f2c3063c2a4390c75d7fe3b1308d34572eaaa016a3b7d08377476e4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.14
|
Release files / pystrometry-0.6.1-py3-none-any.whl
| Download URL | pystrometry-0.6.1-py3-none-any.whl |
|---|---|
| Size | 93.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c1494371e753a43aaf6a72a1e9fe244a653498f7c64f970b001e8ab12620b55
|
|
BLAKE2b-256 checksum How to use checksums |
c9868d4ecfdfec4fcc7c7aa7f1db23d4c26f3240b65d36283927271f624b2e7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.14
|
Security for pystrometry 0.6.1
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.
