pypi-release is created to publish pypi packages to Pinrepo, Pinterest Build Artifact Repository.
Use the following command to publish a python package:
pypi-release -b PYPIREPO_BUCKET -i AWS_ACCESS_KEY_ID -k AWS_SECRET_ACCESS_KEY -f sample-package-1.0.0.tar.gz
Usage:
usage: pypi-release.py [-h] [-f FILE_PATH] [-i AWS_ACCESS_KEY_ID]
[-k AWS_SECRET_ACCESS_KEY] -b BUCKET [-m MAX_ENTRY]
[--regenerate-index] [-p PACKAGE_NAME] [-d WORK_DIR]
[--force] [--dry-run]
Release python packages to Pypi Pinrepo.
optional arguments:
-h, --help show this help message and exit
-f FILE_PATH, --file-path FILE_PATH
the full path of the package to be released
-i AWS_ACCESS_KEY_ID, --aws-access-key-id AWS_ACCESS_KEY_ID
AWS access key id; if not provided, will use
environment variable AWS_ACCESS_KEY_ID
-k AWS_SECRET_ACCESS_KEY, --aws-secret-access-key AWS_SECRET_ACCESS_KEY
AWS secret access key; if not provided, will use
environment variable AWS_SECRET_ACCESS_KEY
-b BUCKET, --bucket BUCKET
AWS bucket holding all the python packages.
-m MAX_ENTRY, --max-entry MAX_ENTRY
the max number of versions to keep in index.html,
default is unlimited.
--regenerate-index [re]generate the index.html for a package,
package_name is needed.
-p PACKAGE_NAME, --package_name PACKAGE_NAME
the name of the package to regenerate index.html for
-d WORK_DIR, --work-dir WORK_DIR
the directory to save intermediate files, default is
/tmp.
--force force to release the same version again, will
overwrite the existing one.
--dry-run will not update anything, just a sanity test.
Metadata
Release files for pypi-release 1.0.2
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 | |
|---|---|---|---|---|
| pypi-release-1.0.2.tar.gz | 9.7 kB | Without provenance | Details |
Release files / pypi-release-1.0.2.tar.gz
| Download URL | pypi-release-1.0.2.tar.gz |
|---|---|
| Size | 9.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b827f5d382564936fbcec963213f3f7705860e2c31088c50d0f6ab803d1941c
|
|
BLAKE2b-256 checksum How to use checksums |
2948bb0d85194e01248fc7f1d581c3eea79330ad05ef36b11eec1eba508a213e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.56.2 CPython/3.9.6
|
Security for pypi-release 1.0.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.