packaging.python.org
packaging.python.org copied to clipboard
Python Packaging User Guide
---- 📚 Documentation preview 📚: https://python-packaging-user-guide--1775.org.readthedocs.build/en/1775/
The core-metadata documentation currently implies that `Requires-Dist` can only use name-based specifiers, but then references PEP 508 which allows for URL based specifiers. Update the documentation to reflect this alternative...
### Issue Description I'm writing a build backend which aims to deliver these key features relevant to the discussion (among others): 1. Sdists will only contain static metadata; 2. The...
updates: - [github.com/astral-sh/ruff-pre-commit: v0.7.1 → v0.8.6](https://github.com/astral-sh/ruff-pre-commit/compare/v0.7.1...v0.8.6) ---- 📚 Documentation preview 📚: https://python-packaging-user-guide--1772.org.readthedocs.build/en/1772/
### Issue Description [The specification page for source distributions](https://packaging.python.org/en/latest/specifications/source-distribution-format/) states the following: > The file name of a sdist was standardised in PEP 625. The file name must be in...
Upon converting a package to src structure, a user is left unable to run their code via the normal python command, `python src/awesome_project/__main__.py` This PR adds an alternative approach that...
Document that building the dists in the same job as publishing is unsupported @ GHA publishing guide
Initially reported here: https://github.com/pypa/gh-action-pypi-publish/issues/237
Hi Thank you for all the great work you do on the Python Packaging User Guide. It really helps the Python community a lot! I have a suggestion: could you...
### Issue Description The [compatibility tag section of the documentation](https://packaging.python.org/en/latest/specifications/platform-compatibility-tags/#use) is lifted directly from PEP-425 and covers how compatibility tags are constructed. However, it is incomplete **and inaccurate** regarding how...
https://github.com/pypa/packaging.python.org/blob/main/source/tutorials/installing-packages.rst says > [:ref:`virtualenv`](https://github.com/pypa/packaging.python.org/blob/main/source/tutorials/installing-packages.rst#id39) needs to be installed separately, but supports Python 2.7+ and Python 3.3+, and [:ref:`pip`](https://github.com/pypa/packaging.python.org/blob/main/source/tutorials/installing-packages.rst#id41), [:ref:`setuptools`](https://github.com/pypa/packaging.python.org/blob/main/source/tutorials/installing-packages.rst#id43) and [:ref:`wheel`](https://github.com/pypa/packaging.python.org/blob/main/source/tutorials/installing-packages.rst#id45) are always installed into created virtual environments by default...