# Standards

**URL:** https://discuss.python.org/c/packaging/std/35.md?page=2

[Latest](https://discuss.python.org/latest.md) · [Categories](https://discuss.python.org/categories.md) · [Tags](https://discuss.python.org/tags.md)

**Page:** 3

---

## [How to vendor a package into a python distribution?](https://discuss.python.org/t/how-to-vendor-a-package-into-a-python-distribution/80844)

<div class="topic-metadata">

**Author:** [@mattip](https://discuss.python.org/u/mattip)\
**Replies:** 45\
**Last updated:** [February 22, 2025, 2:23pm UTC](https://discuss.python.org/t/how-to-vendor-a-package-into-a-python-distribution/80844 "2025-02-22T14:23:58Z")

</div>

Over at PyPy, we vendor cffi, hpy, greenlet, and readline into the distribution we distribute\[1\]. This causes problems for package managers like poetry When importlib.metadata.distributions() reports them as “installed p…

---

## [(pre-publish) PEP 771: Default Extras for Python Software Packages](https://discuss.python.org/t/pre-publish-pep-771-default-extras-for-python-software-packages/77892)

<div class="topic-metadata">

**Author:** [@dustin](https://discuss.python.org/u/dustin)\
**Replies:** 64\
**Last updated:** [February 6, 2025, 10:20pm UTC](https://discuss.python.org/t/pre-publish-pep-771-default-extras-for-python-software-packages/77892 "2025-02-06T22:20:18Z")

</div>

\[BIG UPDATE\] The PEP PR is live: PEP 771: Default Extras for Python Software Packages by astrofrog · Pull Request #4198 · python/peps · GitHub We have been fairly at hard work with @trobitaille. We published and opene…

---

## [Does the Simple repository API version 1.3 exist?](https://discuss.python.org/t/does-the-simple-repository-api-version-1-3-exist/79361)

<div class="topic-metadata">

**Author:** [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Replies:** 5\
**Last updated:** [February 4, 2025, 8:25pm UTC](https://discuss.python.org/t/does-the-simple-repository-api-version-1-3-exist/79361 "2025-02-04T20:25:47Z")

</div>

PEP 740 – Index support for digital attestations | peps.python.org said there should be a version 1.3 (presumably because PEP 708 – Extending the Repository API to Mitigate Dependency Confusion Attacks | peps.python.org …

---

## [PEP 759, External Wheel Hosting](https://discuss.python.org/t/pep-759-external-wheel-hosting/66458)

<div class="topic-metadata">

**Author:** [@barry](https://discuss.python.org/u/barry)\
**Replies:** 47\
**Last updated:** [January 31, 2025, 6:49pm UTC](https://discuss.python.org/t/pep-759-external-wheel-hosting/66458 "2025-01-31T18:49:58Z")

</div>

This PEP proposes what I think is a unique approach to safely hosting external wheels, while keeping PyPI as the source of truth for project and release metadata. The PEP proposes a new uploadable file format, easily …

---

## [Explicitly requiring \`.dist-info\` and \`.data\` in wheel files use normalized name and version](https://discuss.python.org/t/explicitly-requiring-dist-info-and-data-in-wheel-files-use-normalized-name-and-version/77275)

<div class="topic-metadata">

**Author:** [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Replies:** 7\
**Last updated:** [January 21, 2025, 12:26pm UTC](https://discuss.python.org/t/explicitly-requiring-dist-info-and-data-in-wheel-files-use-normalized-name-and-version/77275 "2025-01-21T12:26:49Z")

</div>

It came up on Discord thanks to @henryiii that the spec don’t explicitly state the the name and version used for .dist-info and .data in a wheel file should be normalized. But as @uranusjr pointed out, it’s implied by th…

---

## [PEP 708 - Extending the Repository API to Mitigate Dependency Confusion Attacks](https://discuss.python.org/t/pep-708-extending-the-repository-api-to-mitigate-dependency-confusion-attacks/24179)

<div class="topic-metadata">

**Author:** [@dstufft](https://discuss.python.org/u/dstufft)\
**Replies:** 99\
**Last updated:** [January 17, 2025, 4:33pm UTC](https://discuss.python.org/t/pep-708-extending-the-repository-api-to-mitigate-dependency-confusion-attacks/24179 "2025-01-17T16:33:07Z")

</div>

Following on from the mapping file proposal, which spun off into a thread on pip’s issue tracker, I’ve written up a PEP that I think will allow us to ultimately solve dependency confusion attacks. It takes the approach o…

---

## [Towards standardizing cross compiling](https://discuss.python.org/t/towards-standardizing-cross-compiling/10357)

<div class="topic-metadata">

**Author:** [@benfogle](https://discuss.python.org/u/benfogle)\
**Replies:** 31\
**Last updated:** [January 14, 2025, 6:48pm UTC](https://discuss.python.org/t/towards-standardizing-cross-compiling/10357 "2025-01-14T18:48:49Z")

</div>

I am the maintainer of crossenv, a tool that creates a special virtual environment such that once set up, pip wheel numpy will cross-compile a wheel for a different architecture. While this is definitely a niche tool, it…

---

## [PEP 751: now with graphs!](https://discuss.python.org/t/pep-751-now-with-graphs/69721)

<div class="topic-metadata">

**Author:** [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Replies:** 251\
**Last updated:** [January 11, 2025, 12:07am UTC](https://discuss.python.org/t/pep-751-now-with-graphs/69721 "2025-01-11T00:07:53Z")

</div>

After the discussion in PEP 751: lock files (again), I have updated PEP 751 in three key ways: It stores the dependency graph instead of a set of package versions It records the known entry points into the dependency g…

---

## [Is there a pyproject standard for sources specification of packages?](https://discuss.python.org/t/is-there-a-pyproject-standard-for-sources-specification-of-packages/73723)

<div class="topic-metadata">

**Author:** [@anon81459992](https://discuss.python.org/u/anon81459992)\
**Replies:** 3\
**Last updated:** [December 9, 2024, 6:00pm UTC](https://discuss.python.org/t/is-there-a-pyproject-standard-for-sources-specification-of-packages/73723 "2024-12-09T18:00:24Z")

</div>

Reading astral/uv docs I find: Sources are only respected by uv. If another tool is used, only the definitions in the standard project tables will be used. Here is an example: \[project\] dependencies = \["httpx"\] \[to…

---

## [Proposal: Intersect and Disjoint Operations for Python Version Specifiers](https://discuss.python.org/t/proposal-intersect-and-disjoint-operations-for-python-version-specifiers/71888)

<div class="topic-metadata">

**Author:** [@notatallshaw](https://discuss.python.org/u/notatallshaw)\
**Replies:** 38\
**Last updated:** [November 22, 2024, 9:54pm UTC](https://discuss.python.org/t/proposal-intersect-and-disjoint-operations-for-python-version-specifiers/71888 "2024-11-22T21:54:26Z")

</div>

This is loosely a follow up to “Handling of Pre-Releases when backtracking” with a proposal that helps (but doesn’t solve) that situation, and in general makes it easier for Python package resolvers to agree on handling …

---

## [PEP 751: lock files (again)](https://discuss.python.org/t/pep-751-lock-files-again/59173)

<div class="topic-metadata">

**Author:** [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Replies:** 352\
**Last updated:** [October 10, 2024, 9:24pm UTC](https://discuss.python.org/t/pep-751-lock-files-again/59173 "2024-10-10T21:24:56Z")

</div>

This was all last discussed in Lock files, again (but this time w/ sdists!) . Probably the biggest change since the initial post of that topic is adding support for per-package locking instead of only per-file locking …

---

## [PEP 735: Dependency Groups in pyproject.toml](https://discuss.python.org/t/pep-735-dependency-groups-in-pyproject-toml/39233)

<div class="topic-metadata">

**Author:** [@sirosen](https://discuss.python.org/u/sirosen)\
**Replies:** 351\
**Last updated:** [October 29, 2024, 3:53pm UTC](https://discuss.python.org/t/pep-735-dependency-groups-in-pyproject-toml/39233 "2024-10-29T15:53:34Z")

</div>

Hi all! This is my attempt to follow up on Projects that aren't meant to generate a wheel and \`pyproject.toml\` . Some notes and questions to seed discussion: I have mostly stayed close to @brettcannon’s proposed s…

---

## [PEP 753: Uniform project URLs in core metadata](https://discuss.python.org/t/pep-753-uniform-project-urls-in-core-metadata/62792)

<div class="topic-metadata">

**Author:** [@woodruffw](https://discuss.python.org/u/woodruffw)\
**Replies:** 31\
**Last updated:** [October 10, 2024, 4:15pm UTC](https://discuss.python.org/t/pep-753-uniform-project-urls-in-core-metadata/62792 "2024-10-10T16:15:39Z")

</div>

This is a discussion thread for PEP 753: Uniform URLs in core metadata. Summary: The PEP proposes deprecating the Home-page and Download-URL headers in favor of well-known labels within the already-standardized Project-…

---

## [PEP 711: PyBI: a standard format for distributing Python Binaries](https://discuss.python.org/t/pep-711-pybi-a-standard-format-for-distributing-python-binaries/25547)

<div class="topic-metadata">

**Author:** [@njs](https://discuss.python.org/u/njs)\
**Replies:** 110\
**Last updated:** [October 8, 2024, 3:11pm UTC](https://discuss.python.org/t/pep-711-pybi-a-standard-format-for-distributing-python-binaries/25547 "2024-10-08T15:11:00Z")

</div>

Hey all, finally got around to posting this properly! If anyone else is excited about making this real, I could very much use some help with two things: Cleaning up my janky PyBI building code (the Windows and macOS …

---

## [Idea: Allow optional dependencies to specify other optional dependencies](https://discuss.python.org/t/idea-allow-optional-dependencies-to-specify-other-optional-dependencies/63652)

<div class="topic-metadata">

**Author:** [@notatallshaw](https://discuss.python.org/u/notatallshaw)\
**Replies:** 7\
**Last updated:** [September 18, 2024, 12:17am UTC](https://discuss.python.org/t/idea-allow-optional-dependencies-to-specify-other-optional-dependencies/63652 "2024-09-18T00:17:39Z")

</div>

Optional dependencies currently look like this: Writing your pyproject.toml - Python Packaging User Guide \[project.optional-dependencies\] gui = \["PyQt5"\] cli = \["rich", "click"\] But a very common practise if for option…

---

## [Enforcing consistent metadata for packages](https://discuss.python.org/t/enforcing-consistent-metadata-for-packages/50008)

<div class="topic-metadata">

**Author:** [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Replies:** 112\
**Last updated:** [September 10, 2024, 5:49pm UTC](https://discuss.python.org/t/enforcing-consistent-metadata-for-packages/50008 "2024-09-10T17:49:09Z")

</div>

One of the longer-term goals in the packaging ecosystem has been a move towards statically defined package metadata, with the ultimate intention that tools can read package metadata without any need to execute Python cod…

---

## [Record the top-level names of a wheel in \`METADATA\`?](https://discuss.python.org/t/record-the-top-level-names-of-a-wheel-in-metadata/29494)

<div class="topic-metadata">

**Author:** [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Replies:** 71\
**Last updated:** [August 31, 2024, 12:07pm UTC](https://discuss.python.org/t/record-the-top-level-names-of-a-wheel-in-metadata/29494 "2024-08-31T12:07:48Z")

</div>

I had another instance where I wished I could map a project name to the modules and packages they provide. I also realized that I suspect people come to PyPI looking for a project by its import name and is not always suc…

---

## [PEP 710 - Recording the provenance of installed packages](https://discuss.python.org/t/pep-710-recording-the-provenance-of-installed-packages/25428)

<div class="topic-metadata">

**Author:** [@fridex](https://discuss.python.org/u/fridex)\
**Replies:** 61\
**Last updated:** [August 15, 2024, 2:45pm UTC](https://discuss.python.org/t/pep-710-recording-the-provenance-of-installed-packages/25428 "2024-08-15T14:45:28Z")

</div>

Hi all, following the discussion in Draft PEP: Recording provenance of installed packages, sharing PEP 710 with you. The mentioned PEP 710 can be viewed online. Attaching also PEP below. The PEP was written thanks to …

---

## [Are build backends that use different keyword arguments to the standard spec compliant?](https://discuss.python.org/t/are-build-backends-that-use-different-keyword-arguments-to-the-standard-spec-compliant/53056)

<div class="topic-metadata">

**Author:** [@notatallshaw](https://discuss.python.org/u/notatallshaw)\
**Replies:** 4\
**Last updated:** [July 20, 2024, 7:11pm UTC](https://discuss.python.org/t/are-build-backends-that-use-different-keyword-arguments-to-the-standard-spec-compliant/53056 "2024-07-20T19:11:34Z")

</div>

An interesting issue popped up on uv’s issue tracker. cryptacular 1.6.2 fails to build because the build backend uses they keyword “settings” instead of “config\_settings” for the prepare metadata for build wheel call. Th…

---

## [PEP 740: Index support for digital attestations](https://discuss.python.org/t/pep-740-index-support-for-digital-attestations/44498)

<div class="topic-metadata">

**Author:** [@woodruffw](https://discuss.python.org/u/woodruffw)\
**Replies:** 25\
**Last updated:** [July 17, 2024, 10:17pm UTC](https://discuss.python.org/t/pep-740-index-support-for-digital-attestations/44498 "2024-07-17T22:17:35Z")

</div>

Draft PEP: PEP 740 – Index support for digital attestations | peps.python.org Other context: Pre-PEP: Exposing Trusted Publisher provenance on PyPI To summarize the rationale and motivation: Previous efforts to host…

---

## [Preventing unwanted attempts to build sdists](https://discuss.python.org/t/preventing-unwanted-attempts-to-build-sdists/54169)

<div class="topic-metadata">

**Author:** [@geofft](https://discuss.python.org/u/geofft)\
**Replies:** 75\
**Last updated:** [June 29, 2024, 12:30am UTC](https://discuss.python.org/t/preventing-unwanted-attempts-to-build-sdists/54169 "2024-06-29T00:30:39Z")

</div>

pypackaging-native has a very good writeup “Unsuspecting users getting failing from-source builds” that describes one of the practical usability problems with the pip/PyPI ecosystem. In brief, there are several popular p…

---

## [How to reinvent the wheel](https://discuss.python.org/t/how-to-reinvent-the-wheel/54106)

<div class="topic-metadata">

**Author:** [@emmatyping](https://discuss.python.org/u/emmatyping)\
**Replies:** 32\
**Last updated:** [June 26, 2024, 11:15pm UTC](https://discuss.python.org/t/how-to-reinvent-the-wheel/54106 "2024-06-26T23:15:06Z")

</div>

Breaking this discussion out from the PEP 778 discussion, because this does end up needing to be figured out first. I had originally hoped that a “wheel 2.0” could be a collection of PEPs describing a group of changes i…

---

## [Two extensions/clarifications of PEP 517?](https://discuss.python.org/t/two-extensions-clarifications-of-pep-517/54464)

<div class="topic-metadata">

**Author:** [@thejcannon](https://discuss.python.org/u/thejcannon)\
**Replies:** 19\
**Last updated:** [June 26, 2024, 9:15pm UTC](https://discuss.python.org/t/two-extensions-clarifications-of-pep-517/54464 "2024-06-26T21:15:29Z")

</div>

Background I have two related extensions/clarifications I’m interesting in making to PEP 517, although I am fully aware that there is much history here. Instead of putting a PEP forth (even for discussion) I’m interestin…

---

## [How would you like to declare runtime dependencies and Python requirements for PEP 723?](https://discuss.python.org/t/how-would-you-like-to-declare-runtime-dependencies-and-python-requirements-for-pep-723/40418)

<div class="topic-metadata">

**Author:** [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Replies:** 92\
**Last updated:** [June 24, 2024, 7:20pm UTC](https://discuss.python.org/t/how-would-you-like-to-declare-runtime-dependencies-and-python-requirements-for-pep-723/40418 "2024-06-24T19:20:53Z")

</div>

I think there are essentially three options that have been floated. Option 1 What’s in PEP 723: a new \[run\] table with dependencies and requires-python. \[run\] requires-python = "\>=3.12" dependencies = \["requests", "tex…

---

## [PEP 722/723 decision](https://discuss.python.org/t/pep-722-723-decision/36763)

<div class="topic-metadata">

**Author:** [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Replies:** 120\
**Last updated:** [June 20, 2024, 4:11pm UTC](https://discuss.python.org/t/pep-722-723-decision/36763 "2024-06-20T16:11:00Z")

</div>

So this was not an easy decision to make between PEP 722 and PEP 723, making it hard to be the PEP delegate (and that’s ignoring all of the controversy surrounding me being the delegate to begin with). I think pretty muc…

---

## [PEP 668: Marking Python base environments as "externally managed"](https://discuss.python.org/t/pep-668-marking-python-base-environments-as-externally-managed/10302)

<div class="topic-metadata">

**Author:** [@geofft](https://discuss.python.org/u/geofft)\
**Replies:** 116\
**Last updated:** [May 28, 2024, 1:05pm UTC](https://discuss.python.org/t/pep-668-marking-python-base-environments-as-externally-managed/10302 "2024-05-28T13:05:34Z")

</div>

At the “Linux in Distros” sprint at PyCon US in May, we drafted a PEP about making external package managers like apt/dnf/etc. and Python-specific package managers like pip play more nicely together. This includes the “s…

---

## [Extending PEP 508: support dependencies in environment markers](https://discuss.python.org/t/extending-pep-508-support-dependencies-in-environment-markers/53725)

<div class="topic-metadata">

**Author:** [@adamjstewart](https://discuss.python.org/u/adamjstewart)\
**Replies:** 12\
**Last updated:** [May 21, 2024, 2:48pm UTC](https://discuss.python.org/t/extending-pep-508-support-dependencies-in-environment-markers/53725 "2024-05-21T14:48:05Z")

</div>

I would like to propose extending PEP 508 to also allow for dependencies to appear in environment markers. An example syntax in pyproject.toml might look like: dependencies = \[ "a", "b", "a\<2;b\<1", \] In th…

---

## [Is Provides-Extra necessary for 'doc' and 'test' extras?](https://discuss.python.org/t/is-provides-extra-necessary-for-doc-and-test-extras/53689)

<div class="topic-metadata">

**Author:** [@jaraco](https://discuss.python.org/u/jaraco)\
**Replies:** 2\
**Last updated:** [May 19, 2024, 8:02pm UTC](https://discuss.python.org/t/is-provides-extra-necessary-for-doc-and-test-extras/53689 "2024-05-19T20:02:18Z")

</div>

I’m attempting to build a package with some test and doc dependencies. According to the spec: The specified name may be used to make a dependency conditional on whether the optional feature has been requested. … Two …

---

## [PEP 639, Round 2: Improving license clarity with better package metadata](https://discuss.python.org/t/pep-639-round-2-improving-license-clarity-with-better-package-metadata/12622)

<div class="topic-metadata">

**Author:** [@CAM-Gerlach](https://discuss.python.org/u/CAM-Gerlach)\
**Replies:** 113\
**Last updated:** [May 10, 2024, 12:23pm UTC](https://discuss.python.org/t/pep-639-round-2-improving-license-clarity-with-better-package-metadata/12622 "2024-05-10T12:23:30Z")

</div>

PEP 639, describing the proposed new License-Expression and License-File metadata fields, was recently thoroughly rewritten to implement the major additions and changes agreed upon in the previous thread, add the corresp…

---

## [Lock files, again (but this time w/ sdists!)](https://discuss.python.org/t/lock-files-again-but-this-time-w-sdists/46593)

<div class="topic-metadata">

**Author:** [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Replies:** 309\
**Last updated:** [March 18, 2024, 1:43pm UTC](https://discuss.python.org/t/lock-files-again-but-this-time-w-sdists/46593 "2024-03-18T13:43:44Z")

</div>

Two years since PEP 665 was rejected and three years since I started working towards some lock file solution, I present my next (and last regardless of outcome) attempt at coming up with a lock file standard. Terms “pl…

[Previous page](https://discuss.python.org/c/packaging/std/35.md?page=1)

[Next page](https://discuss.python.org/c/packaging/std/35.md?page=3)
