Introduction
This is a plugin for zest.releaser for being able to automatically copy releases of your products to a local directory.
This can be useful in some special customer environments, for example behind strong firewall and network policies, where reaching an external pypi repository is not simple.
How to use
You must configure your ~/.pypirc file, adding to it a configuration like the one that follow:
[rt.zestreleaser.pypilocal] pypi-local = ../../pypi-local
In this example next time you will run the fullrelease utility, a folder named pypi-local will be searched two level above the current working directory.
In a common buildout environment this is a normal situation:
buildout-directory
|
...
|_ pypi-local
...
\_ src
|
...
\_ your.package
It this way the pypi-local folder will be looked in the buildout directory root.
You can also provide multiple path, or system absolute paths:
[rt.zestreleaser.pypilocal] pypi-local = ../../pypi-local global = /opt/global-pypi
For every found match, zest.releaser will ask to you if copy the release in the folder:
.... Register and upload to pypi (y/N)? Register and upload to plone.org (Y/n)? n Copy egg to folder /Users/keul/buildout/test/pypi-local (Y/n)? Y Copy egg to folder /opt/global-pypi (Y/n)?
Changelog
0.2 (2022-12-22)
Python3 support. [cekk]
0.1 (2013-01-30)
Initial release [keul]
Metadata
Release files for rt.zestreleaser.pypilocal 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 | Actions |
|---|---|---|---|---|
| rt.zestreleaser.pypilocal-0.2.tar.gz | 13.1 kB | Without provenance | Details for rt.zestreleaser.pypilocal-0.2.tar.gz |
Release files / rt.zestreleaser.pypilocal-0.2.tar.gz
| Download URL | rt.zestreleaser.pypilocal-0.2.tar.gz |
|---|---|
| Size | 13.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c9462aedfe9d4276b279f711f4da8fbf37f56231f1e2d19c1c4afabcf36ee6bd
|
|
BLAKE2b-256 checksum How to use checksums |
e197d4160503c1ebc22a8373a292400be5c4f837f0ed2a46d500968df6f84ded
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.12
|
Security for rt.zestreleaser.pypilocal 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.