Pylease
Pylease is a simple package that tends to ease the release process of a regular Python package. The aim of Pylease is to make it as simple as possible by requiring as little as possible. For more details on using Pylease please see the documentation.
Basic Usage
Start using pylease by just navigating to you package root (the directory containing setup.py) and simply use the command-line:
$ pylease status
Now you will see basic information about your package, like name and version. Then take a try and do:
$ pylease make --dev
This will release the package with version ‘1.0.dev1’, i.e. update the version in setup.py. The release levels include major, minor, patch and dev.
If you want to initiate a branch new project, perform this:
$ pylease init my_project
This will prepare and create all needed files and directories for your project skeleton.
Extensions
Pylease also comes with extensions mechanisms. It includes some useful extensions that might be used in combination as well as anyone can write extensions for Pylease to enhance it.
Git
Git extension provides functionality to automatically create a tag on the git repository associated with the version, and commit the changes made to the setup.py.
This may be achieved by simply adding --git-tag argument while calling pylease:
$ pylease make --minor --git-tag
After making the release, you will additionally have a new commit containing the setup.py update as well as a new tag pointing to that commit.
PyPI
PyPI extension provides an ability to automatically upload you package distribution to PyPi after releasing your project. To enable this feature use the --pypi command line option:
$ pylease make --major --pypi
Metadata
Release files for pylease 0.3.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 |
|---|---|---|---|---|
| pylease-0.3.2.tar.gz | 22.0 kB | Without provenance | Details for pylease-0.3.2.tar.gz |
Release files / pylease-0.3.2.tar.gz
| Download URL | pylease-0.3.2.tar.gz |
|---|---|
| Size | 22.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9f519d123f899dc85017a7ab9dadeacfc4ae7763eed8b0b19374fcc188a2c46
|
|
BLAKE2b-256 checksum How to use checksums |
7337ad3f35f7ac3169f3f81fddc54ecb76cab1e40204c2b049ee8d101dd2bbff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pylease 0.3.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.