This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: Avoid confusion with qc-iodata.
IOData
About
License
IOData is distributed under GPL License version 3 (GPLv3).
Dependencies
The following dependencies will be necessary for IOData to build properly,
Python >= 2.7, >= 3.5: http://www.python.org/
SciPy >= 0.11.0: http://www.scipy.org/
NumPy >= 1.9.1: http://www.numpy.org/
Nosetests >= 1.1.2: http://readthedocs.org/docs/nose/en/latest/
Installation
To install IOData:
`bash python ./setup install --user `
Testing
To run tests:
`bash nosetests -v iodata `
Metadata
Release files for iodata 0.1.3
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 |
|---|---|---|---|---|
| iodata-0.1.3.tar.gz | 1.1 MB | Without provenance | Details for iodata-0.1.3.tar.gz |
Release files / iodata-0.1.3.tar.gz
| Download URL | iodata-0.1.3.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e183639bd346781895e5dd9d363f213b2684249344aa944a7e3882d163b25bc
|
|
BLAKE2b-256 checksum How to use checksums |
00a4d2f415ac3d91767b9cd8b746f4319fbe4b8f392ab24b55deb2805eba3c23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for iodata 0.1.3
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.