poetry-setup
Make your poetry project backward compatible.
This tool generate some files from pyproject.toml:
- setup.py
- requirements.txt
- constraints.txt (from optional dependencies)
Installation
I'm recommend use pipsi for all console scripts like this.
Install via pipsi:
pipsi install poetry-setup
Install via pip:
pip install poetry-setup
Install via poetry:
poetry install poetry-setup
Usage
poetry-setup [path/to/project/]
Generate for project in current dir:
poetry-setup
Generate for project in example dir:
poetry-setup example
What about pipenv?
Pipenv can generate Pipfile from requirements.txt.
Run test
pipenv install
pipenv shell
python -m pytest tests.py
1 maintainer
Metadata
1 maintainer
Release files for poetry-setup 0.3.6
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 |
|---|---|---|---|---|
| poetry-setup-0.3.6.tar.gz | 4.9 kB | Without provenance | Details for poetry-setup-0.3.6.tar.gz |
Release files / poetry-setup-0.3.6.tar.gz
| Download URL | poetry-setup-0.3.6.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18204efc69bc3a79d19c905142d986e76d9a9dd18f4480f336dc6a7aad6a43b3
|
|
BLAKE2b-256 checksum How to use checksums |
372d1470abd025931519bcdd29957dd7fc14cf33217237fce0cdfa350532e771
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/39.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.5.2
|
Security for poetry-setup 0.3.6
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.
