-
Notifications
You must be signed in to change notification settings - Fork 986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guide for "Single sourcing the package version" refers to setup.py #1260
Comments
|
FWIW |
It would be nice, however, to swap the preference in the document. I'd still go for |
There's some excellent lecture about this, maybe this can be linked?
Preference for what do you mean? |
For the main article contents to feature |
@webknjaz To correct some misconceptions:
The plan from setuptools is to eventually deprecate +1 for moving |
thin the page needs updating: See #1273 Please comment / edit that so we can get a nicer page together. |
Resolved in #1612 |
https://packaging.python.org/en/latest/guides/single-sourcing-package-version/ refers to setup.py and the many ways how to get the version into setup.py. pyproject.toml is mentioned only as a side note.
Since setup.py is deprecated in favour of pyproject.toml, I wonder what to do with this document. Single sourcing the version should be a non-issue. We could either strip the whole document down to pyproject.toml which would make the document very small, or move the relevant paragraph into the packaging tutorial:
The text was updated successfully, but these errors were encountered: