packaging.python.org

packaging.python.org copied to clipboard

Update "Dropping older Python versions" guide

2

An attempt to improve the guide. Actually I find the title a bit inaccurate. What about _"Changing required Python versions in the package metadata"_? ---- 📚 Documentation preview 📚: https://python-packaging-user-guide--1471.org.readthedocs.build/en/1471/guides/dropping-older-python-versions/

chrysle

Canonical guide to specifying dependencies?

9

We should probably have a canonical guide to installing dependencies on packaging.python.org, especially since [PEP 508](https://www.python.org/dev/peps/pep-0508/) has changed things like how to link to a git repository. I get a...

pganssle

Import PEP 517 specification

3

This PR builds on top of #1396 (the “pyproject.toml specification”). Contains atomic, separately reviewable commits: - Import PEP 517 verbatim - PEP 517: Trim all rationale/motivation sections - PEP 517:...

jeanas

Restructure table of contents, section indices, and landing page

5

This PR applies Diataxis structure consistently to the guide's contents. It simplifies the landing page and the main contents sidebar. | CURRENT | PR | |-----------|----| | | | This...

willingc

Is the section about `setuptools` and `wheel` required to build from source still relevant?

4

I just came across [this section](https://packaging.python.org/en/latest/tutorials/installing-packages/#ensure-pip-setuptools-and-wheel-are-up-to-date) which states: > While `pip` alone is sufficient to install from pre-built binary archives, up to date copies of the `setuptools` and `wheel` projects...

Viicos

Add discussion on `__main__.py` vs. `__init__.py` files

6

This ought to be a valuable extension regarding guidance on how to structure a Python package. There is often dissent about what to store in and when to use these...

chrysle

Example from docs for "Installing from VCS" does not work

3

[Installing from VCS](https://packaging.python.org/en/latest/tutorials/installing-packages/#installing-from-vcs) example says, that `python3 -m pip install -e SomeProject @ git+https://git.repo/some_pkg.git` command should install package in editable mode from VCS. Tested on Mac Ventura 13.1, on both...

alvassin

https://peps.python.org/pep-0566/#json-compatible-metadata ---- 📚 Documentation preview 📚: https://python-packaging-user-guide--1466.org.readthedocs.build/en/1466/specifications/core-metadata/#transforming-core-metadata-to-json

jeanas

Document special casing pip entrypoints

2

When installing entrypoints, [pip special cases itself](https://github.com/pypa/pip/blob/3898741e29b7279e7bffe044ecfbe20f6a438b1e/src/pip/_internal/operations/install/wheel.py#L283): It will always create `pip`, `pip{major}` and `pip{major}.{minor}` entrypoints, even the universal pip wheel has hardcoded `pip`, `pip3` and `pip3.10` entrypoints (https://inspector.pypi.io/project/pip/24.0/packages/8a/6a/19e9fe04fca059ccf770861c7d5721ab4c2aebc539889e97c7977528a53b/pip-24.0-py3-none-any.whl/pip-24.0.dist-info/entry_points.txt). It...

konstin

Is the recommendation to use metadata python.integrator for local versions outdated?

2

The last section in https://packaging.python.org/en/latest/specifications/version-specifiers/#local-version-identifiers says > **Local version identifiers** > [...] > Source distributions using a local version identifier SHOULD provide the `python.integrator` extension metadata (as defined in [PEP...

schaetzc