setuptools-pyproject-migration
Introduction
pyproject.toml represents the new era of Python packaging, but many old
projects are still using setuptools. That's where this package comes in: just
install it, run it, and it will print out a nicely formatted pyproject.toml
file with the same metadata that you had in setup.py or setup.cfg.
Or at least, that's the goal. The project is currently a work in progress with only partial support for all the attributes that might exist in a setuptools configuration, so this won't yet work for anything complex. Feel free to file an issue to highlight anything that needs to be added!
Installation and usage
There are two different ways to install this project. You can use either or both depending on what you prefer.
Standalone application
To install setuptools-pyproject-migration as an application, we recommend
using pipx (though of course you can also do
this with pip install --user or in a virtual environment of your choice).
First make sure you have pipx installed, then run
pipx install setuptools-pyproject-migration
After that, in any directory that has a setup.py and/or setup.cfg file, you
can run
setuptools-pyproject-migration
and it will print out the content of pyproject.toml as computed from your
setup.py and/or setup.cfg. Running setuptools-pyproject-migration -h will
print a brief usage summary.
You can also install and run the application in one go as follows:
pipx run setuptools-pyproject-migration
Virtual environment
Or you can use setuptools-pyproject-migration in a virtual environment you use
to develop your project. Activate your virtual environment and then run
python -m pip install setuptools-pyproject-migration
and then running
python setup.py pyproject
will print out the content of your pyproject.toml file.
History
Inspired by a conversation on Mastodon.
Metadata
Release files for setuptools-pyproject-migration 0.3.1.post0
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 |
|---|---|---|---|---|
| setuptools_pyproject_migration-0.3.1.post0.tar.gz | 59.3 kB | Without provenance | Details for setuptools_pyproject_migration-0.3.1.post0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| setuptools_pyproject_migration-0.3.1.post0-py3-none-any.whl | Python 3 | none | any | Details for setuptools_pyproject_migration-0.3.1.post0-py3-none-any.whl |
Total release size: 74.3 kB
Release files / setuptools_pyproject_migration-0.3.1.post0.tar.gz
| Download URL | setuptools_pyproject_migration-0.3.1.post0.tar.gz |
|---|---|
| Size | 59.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3047028232ad14fbfa8421aace0d7d3724e97d957aaccf6d785f119a72a49f4
|
|
BLAKE2b-256 checksum How to use checksums |
96c617d4cd8286263164c26728fc579c2d83f11cbe7f2049ad49a667305c2ab1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.5
|
Release files / setuptools_pyproject_migration-0.3.1.post0-py3-none-any.whl
| Download URL | setuptools_pyproject_migration-0.3.1.post0-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b4c696fba2945ac85d56103a858724085cae398235ae0be455722b3426f0d0f
|
|
BLAKE2b-256 checksum How to use checksums |
bd967c5acb3f4e5dff06db2bbcba7336eaabc5f40c29331c147f56efb65e2682
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.5
|
Security for setuptools-pyproject-migration 0.3.1.post0
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.