ps.releaser
ps.releaser provides several plugins for zest.releaser. The plugins are registered globally and can be activated if needed.
Available Plugins
Exportig Diazo Themes as ZIP files
Plone allows us to upload diazo themes as zip files. This can be used when we don’t have the permission to install our theme on the server as a python package (e.g. within a shared hosting environment). ps.releaser provides a hook which is run after the release has been done. Use the following options in your setup.cfg to enable the ZIP file export:
[ps.releaser] diazo_export.enabled = 1 diazo_export.path = src/my/package/diazo_resources diazo_export.adjust_title = 1
- diazo_export.enabled
Activate or deactivate the export.
- diazo_export.path
Path relative from the package root to the folder containing the diazo resource files.
- diazo_export.adjust_title
Append the version number of the package to the title in the zipped manifest.cfg file.
Installation
Use in a buildout
[buildout]
parts += releaser
[releaser]
recipe = z3c.recipe.scripts
dependent-scripts = true
eggs =
ps.releaser
my.package
If you want to use the latest development version from GitHub, add ps.releaser to your mr.developer source section:
[buildout] extensions += mr.developer [sources] ps.releaser = git git@github.com:propertyshelf/ps.releaser.git
This creates the zest.releaser executables in your bin-directory. Create a release as you’re used to:
$ ./bin/fullrelease
Installation in a virtualenv
You can also install ps.releaser in a virtualenv.:
$ pip install ps.releaser
You can also install the latest version of ps.releaser directly from GitHub:
$ pip install -e git@github.com:propertyshelf/ps.releaser.git#egg=ps.releaser
Now you can use it like this (when releasing your package):
$ fullrelease
Changelog
0.3 (2016-02-08)
Added console script to only release diazo theme as zip.
0.2 (2015-03-03)
Use the diazo_export prefix for settings related to diazo zip file export.
0.1 (2015-03-02)
Initial release.
Metadata
Release files for ps.releaser 0.3
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 |
|---|---|---|---|---|
| ps.releaser-0.3.zip | 13.8 kB | Without provenance | Details for ps.releaser-0.3.zip |
Release files / ps.releaser-0.3.zip
| Download URL | ps.releaser-0.3.zip |
|---|---|
| Size | 13.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e3ff4ed8aaaf9aee1041839541534763e5408e2eaa1f539ea1255595e13eb3c
|
|
BLAKE2b-256 checksum How to use checksums |
7cd855026363f7b347a9efa924ba2cfc2be3165e497461ece9f16f1d50a07590
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ps.releaser 0.3
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.