########## Instructions for updating DDR infrastructure files #################
Make changes in ddr infrastructure files
cd ~/ddr-home/ddr-clips/ddr-packaging/ edit setup.py for new ddr-clips version number rm -rf dist python3 -m build cp ~/ddr-home/ddr-clips/ddr-packaging/dist/ddr_clips-x.y.z-py3-none-any.whl ddr-home/ddr-clips/infra/xe/infra-files
cd ~/ddr-home/ddr-python/ddr-packaging/ edit setup.py for new ddr-python version number rm -rf dist python3 -m build cp ~/ddr-home/ddr-python/ddr-packaging/dist/ddr_python-x.y.z-py3-none-any.whl ddr-home/ddr-python/infra/xe/infra-files
Make changes in DDR automation to use the updated ddr-clips and ddr-python packages
Copy new ddr-clips and ddr-python .whl files
rm ~/ddr-home/ddr-lm/files/xe/infra-files/ddr_* cp ~/ddr-home/ddr-clips/ddr-packaging/dist/ddr_clips-x.y.z-py3-none-any.whl ~/ddr-home/ddr-lm/files/xe/infra-files cp ~/ddr-home/ddr-python/ddr-packaging/dist/ddr_python-x.y.z-py3-none-any.whl ~/ddr-home/ddr-lm/files/xe/infra-files
Edit pipfiles.sh to include new ddr-clips and ddr-python .whl names
~/ddr-home/ddr-lm/files/xe/infra-files/pipfiles.sh
Push changes to ddr-clips repository Push changes to ddr-python repository Push changes to ddr-pyats repository
Make changes in ddr-clips and ddr-python usecases
Copy selected usecases that will be used with ddr-pyats
cp ~/ddr-home/ddr-clips/usecases/xe/USECASE_Directory ~/ddr-home/ddr-pyats/usecases/xe cp ~/ddr-home/ddr-python/usecases/xe/USECASE.py ~/ddr-home/ddr-pyats/usecases/xe
update DDR repositories
git add and git commit changes to repositories and push
~/ddr-home/ddr-clips git push ~/ddr-home/ddr-python git push ~/ddr-home/ddr-pyats git push
update ADS machine DDR repositories
Assumes that all repositories are stored on ADS in /nobackup/USERNAME/ddr-home...
/nobackup/USERNAME/ddr-home/ddr-clips git pull /nobackup/USERNAME/ddr-home/ddr-python git pull /nobackup/USERNAME/ddr-home/ddr-pyats git pull
Metadata
Release files for ddr-python 1.0.16
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 |
|---|---|---|---|---|
| ddr-python-1.0.16.tar.gz | 45.3 kB | Without provenance | Details for ddr-python-1.0.16.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ddr_python-1.0.16-py3-none-any.whl | Python 3 | none | any | Details for ddr_python-1.0.16-py3-none-any.whl |
Total release size: 92.2 kB
Release files / ddr-python-1.0.16.tar.gz
| Download URL | ddr-python-1.0.16.tar.gz |
|---|---|
| Size | 45.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad7283a77fd6fc8828956115e2eaed557362b0018dc90e1b3b4a011d2cf01706
|
|
BLAKE2b-256 checksum How to use checksums |
ef8040a35ad7efde45f0823dd470f5e0f587f5098fb548c9fdb3cf23669c84fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Release files / ddr_python-1.0.16-py3-none-any.whl
| Download URL | ddr_python-1.0.16-py3-none-any.whl |
|---|---|
| Size | 46.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
493a90fa1df610153dda65013ad4a11b8c2bacd9eaf41e14ca81bf01cfb33285
|
|
BLAKE2b-256 checksum How to use checksums |
0f0ad836270a3f524b428eeb97de5b4a3861c41e0f203282fd86d23ff255bc37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for ddr-python 1.0.16
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.