nexor
Note: not recommended for GA yet.
The nexor command tries to help reasonable workflow for Python which is build-tool agnostic.
nexor relock: Create requirements-<…>.txt files for all extra dependencies, and a requirements.txt without any extras.
nexor env: Create a virtual environment in WORKON_HOME or, if one already exists, install the dependencies in it from the lock file. By default this is requirements.txt, but you can configure in pyproject.toml under tools.nexor default_extra to be something else.
nexor depend: Add a dependency to pyproject.toml. Also, by default, relock the files and update the env.
You can also add new commands to nexor. [more docs here about how to do it.]
1 maintainer
Metadata
1 maintainer
Release files for nexor 2024.1.19.65996
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 |
|---|---|---|---|---|
| nexor-2024.1.19.65996.tar.gz | 5.7 kB | Without provenance | Details for nexor-2024.1.19.65996.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nexor-2024.1.19.65996-py3-none-any.whl | Python 3 | none | any | Details for nexor-2024.1.19.65996-py3-none-any.whl |
Total release size: 11.9 kB
Release files / nexor-2024.1.19.65996.tar.gz
| Download URL | nexor-2024.1.19.65996.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c59c12bb85aba3d13543ad3ac8c7a9a5a94bd61a44c98590c0bb59e1f18f9739
|
|
BLAKE2b-256 checksum How to use checksums |
72dec6036344ed65c8840af56f23ed5ddc736efe0d0420f0ce049f14584fa5ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.1 CPython/3.11.7
|
Release files / nexor-2024.1.19.65996-py3-none-any.whl
| Download URL | nexor-2024.1.19.65996-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2d0583442ec1a7d945e033a3d72d7843b88fa2e76c7a09441203366e329776a
|
|
BLAKE2b-256 checksum How to use checksums |
d305da4ee2b6ed915ca2ba8648e20bab17d91340ffee88f7f0521c8d37025b07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.1 CPython/3.11.7
|
Security for nexor 2024.1.19.65996
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.
