Deployment instructions
Global
Before deployment, change the project version on setup.py file and set the correct downloadurl_. Then make sure you have the file ~/.pypirc with the content below and the correct credentials instead of the provided placeholders:
[distutils]
index-servers =
pypi
pypitest
[pypi]
repository:https://upload.pypi.org/legacy/
username:myusername
password:mypassword
[pypitest]
repository:https://test.pypi.org/legacy/
username:myusername
password:mypassword
Test environment
Run python setup.py sdist upload -r pypitest inside the project directory.
Live environment
Run python setup.py sdist upload -r pypi inside the project directory.
Metadata
Release files for febraban-cnab 0.0.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 | Actions |
|---|---|---|---|---|
| febraban cnab-0.0.1.tar.gz | 17.2 kB | Without provenance | Details for febraban cnab-0.0.1.tar.gz |
Release files / febraban cnab-0.0.1.tar.gz
| Download URL | febraban cnab-0.0.1.tar.gz |
|---|---|
| Size | 17.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
beefc7b4b3a3644d4d3dc9fec54426550b18ea53d05bc5bc96996b4132d778d4
|
|
BLAKE2b-256 checksum How to use checksums |
61f201f37f03ec1081074a8fe607aad5e3b5e0253ce894e94d5915da316e84c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/28.8.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.2
|
Security for febraban-cnab 0.0.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.