AGX dependency
This is an example project to prove that agxver can be used to retrieve the correct agx dependant pypi package.
Versions
1.1.0 --> 2.36.1.0 1.1.2 --> 2.36.1.2
Prove concept
poetry build -f wheel
pip3.9 install dist/needagx-1.1.2-py3-none-any.whl
Above will fail if agxver-2.36.1.2 is not installed, and will succeed if it is installed.
Choosing version from pypi
Prereqs:
- 1.1.0 is uploaded to pypi depending on 2.36.1.0
- 1.1.2 is uploaded to pypi depending on 2.36.1.2
cd agxver; git checkout 2.36.1.0; cd ..
pip3.0 install agxver
pip3.9 install needagx
# --> needagx 1.1.0 will be installed
cd agxver; git checkout 2.36.1.2; cd ..
pip3.0 install agxver
pip3.9 install needagx
# --> needagx 1.1.2 will be installed
Metadata
Release files for needagx 1.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| needagx-1.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / needagx-1.1.2-py3-none-any.whl
| Download URL | needagx-1.1.2-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c605f4fe13ca39c492e59f5fb3c7c2b4b29c4e03c5817ab05919f533176ff092
|
|
BLAKE2b-256 checksum How to use checksums |
6fa1c5853e7d1419052d8e788bdbb6c9784eaf0e1622fcc8f37c328b0ec5edce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/68.1.2 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.9.18
|
Security for needagx 1.1.2
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.