# \#pep

**URL:** https://discuss.python.org/tag/pep/64.md

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

---

## [PEP 837: Extensible JSON serialization](https://discuss.python.org/t/pep-837-extensible-json-serialization/108124)

<div class="topic-metadata">

**Author:** [@storchaka](https://discuss.python.org/u/storchaka)\
**Replies:** 45\
**Last updated:** [October 23, 2026, 9:43pm UTC](https://discuss.python.org/t/pep-837-extensible-json-serialization/108124 "2026-10-23T21:43:45Z")

</div>

I have submitted PEP 837 (PR python/peps#5031 until it renders), which proposes an extension mechanism for the json encoder. It is a revival and rework of an idea with a long history — the implementation descends from my…

---

## [PEP 817 - Wheel Variants: Beyond Platform Tags](https://discuss.python.org/t/pep-817-wheel-variants-beyond-platform-tags/105860)

<div class="topic-metadata">

**Author:** [@jonathandekhtiar](https://discuss.python.org/u/jonathandekhtiar)\
**Replies:** 298\
**Last updated:** [October 20, 2026, 2:04pm UTC](https://discuss.python.org/t/pep-817-wheel-variants-beyond-platform-tags/105860 "2026-10-20T14:04:24Z")

</div>

We are happy to announce that “PEP 817 – Wheel Variants: Beyond Platform Tags” has been merged and the full text of the PEP is now available at: PEP 817 – Wheel Variants: Beyond Platform Tags | peps.python.org. History …

---

## [None-coalescing operator and null‑coalescing assignment](https://discuss.python.org/t/none-coalescing-operator-and-null-coalescing-assignment/107510)

<div class="topic-metadata">

**Author:** [@Rainwalker](https://discuss.python.org/u/Rainwalker)\
**Replies:** 65\
**Last updated:** [September 21, 2026, 11:14pm UTC](https://discuss.python.org/t/none-coalescing-operator-and-null-coalescing-assignment/107510 "2026-09-21T23:14:42Z")

</div>

\[Pre-PEP\] None-coalescing operator ?? and null-coalescing assignment ??= Author: Rainwalker Target version: Python 3.16 (or later) Status: Pre‑PEP (discussion) Note: This is a narrow subset of PEP 505 (no ?. or ?\[\]). …

---

## [Introduce type keyword for type only imports](https://discuss.python.org/t/introduce-type-keyword-for-type-only-imports/104152)

<div class="topic-metadata">

**Author:** [@curiousfurbytes](https://discuss.python.org/u/curiousfurbytes)\
**Replies:** 16\
**Last updated:** [August 6, 2026, 3:50pm UTC](https://discuss.python.org/t/introduce-type-keyword-for-type-only-imports/104152 "2026-08-06T15:50:42Z")

</div>

After the great work of everyone involved in PEP 810, I would like to propose a new idea that is similar and somewhat changes a bit of the PEP itself, which is the introduction of the type keyword for imports that are on…

---

## [Pre-PEP discussion: revival of PEP 543 - A Unified TLS API for Python](https://discuss.python.org/t/pre-pep-discussion-revival-of-pep-543-a-unified-tls-api-for-python/51263)

<div class="topic-metadata">

**Author:** [@woodruffw](https://discuss.python.org/u/woodruffw)\
**Replies:** 91\
**Last updated:** [August 5, 2026, 2:27pm UTC](https://discuss.python.org/t/pre-pep-discussion-revival-of-pep-543-a-unified-tls-api-for-python/51263 "2026-08-05T14:27:00Z")

</div>

Hi all, We (@jvdprng and myself) are planning to resurrect the previously withdrawn PEP 543 as part of our work with the Sovereign Tech Fund. To this end, we have looked at the history of this PEP, considered what has c…

---

## [PEP 831 – Frame Pointers Everywhere: Enabling System-Level Observability for Python](https://discuss.python.org/t/pep-831-frame-pointers-everywhere-enabling-system-level-observability-for-python/106958)

<div class="topic-metadata">

**Author:** [@pablogsal](https://discuss.python.org/u/pablogsal)\
**Replies:** 6\
**Last updated:** [August 4, 2026, 9:33am UTC](https://discuss.python.org/t/pep-831-frame-pointers-everywhere-enabling-system-level-observability-for-python/106958 "2026-08-04T09:33:02Z")

</div>

Hi everyone! :wave: We are happy to announce PEP 831 – “Frame Pointers Everywhere” This PEP proposes building CPython with -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer by default starting in Python 3.15, so tha…

---

## [Making Python networking competitive with Go using work-stealing](https://discuss.python.org/t/making-python-networking-competitive-with-go-using-work-stealing/108268)

<div class="topic-metadata">

**Author:** [@robertsdotpm](https://discuss.python.org/u/robertsdotpm)\
**Replies:** 2\
**Last updated:** [July 27, 2026, 1:29am UTC](https://discuss.python.org/t/making-python-networking-competitive-with-go-using-work-stealing/108268 "2026-07-27T01:29:13Z")

</div>

The problem: blocking Python’s I/O models all face the same question: what happens when something blocks? Asyncio can be stalled by one slow function. Threads require manual offloading, while processes are expensive and…

---

## [Interactive Graph of PEP authorships](https://discuss.python.org/t/interactive-graph-of-pep-authorships/107626)

<div class="topic-metadata">

**Author:** [@hwelch](https://discuss.python.org/u/hwelch)\
**Replies:** 9\
**Last updated:** [June 4, 2026, 9:19pm UTC](https://discuss.python.org/t/interactive-graph-of-pep-authorships/107626 "2026-06-04T21:19:10Z")

</div>

I’ve been playing around with visjs recently using Python to the graph then just writing the data to an HTML template using jinja. One of my test cases was to try and map out PEPs in some meaningful way. If you’re intere…

---

## [Pre-PEP discussion: typing.tool + inspect.tool\_schema(), close the Zod gap for Python agent dev](https://discuss.python.org/t/pre-pep-discussion-typing-tool-inspect-tool-schema-close-the-zod-gap-for-python-agent-dev/107431)

<div class="topic-metadata">

**Author:** [@mvanhorn](https://discuss.python.org/u/mvanhorn)\
**Replies:** 7\
**Last updated:** [May 20, 2026, 2:40pm UTC](https://discuss.python.org/t/pre-pep-discussion-typing-tool-inspect-tool-schema-close-the-zod-gap-for-python-agent-dev/107431 "2026-05-20T14:40:14Z")

</div>

Hi, I’m Matt Van Horn. Quick intro since this is a substantial proposal. I co-founded what became Lyft, founded the smart oven company June (acquired by Weber), and currently ship a few open-source projects. last30days …

---

## [PEP 830: Add timestamps to exceptions and tracebacks](https://discuss.python.org/t/pep-830-add-timestamps-to-exceptions-and-tracebacks/106942)

<div class="topic-metadata">

**Author:** [@gpshead](https://discuss.python.org/u/gpshead)\
**Replies:** 28\
**Last updated:** [May 4, 2026, 9:11pm UTC](https://discuss.python.org/t/pep-830-add-timestamps-to-exceptions-and-tracebacks/106942 "2026-05-04T21:11:40Z")

</div>

This PEP adds an optional timestamp to all exceptions that records when the exception was instantiated with no observable overhead. When enabled via environment variable or command-line flag, formatted tracebacks display…

---

## [PEP 803: Stable ABI for Free-Threaded Builds (packaging thread)](https://discuss.python.org/t/pep-803-stable-abi-for-free-threaded-builds-packaging-thread/104976)

<div class="topic-metadata">

**Author:** [@encukou](https://discuss.python.org/u/encukou)\
**Replies:** 119\
**Last updated:** [April 23, 2026, 2:36pm UTC](https://discuss.python.org/t/pep-803-stable-abi-for-free-threaded-builds-packaging-thread/104976 "2026-04-23T14:36:43Z")

</div>

Hello, tool authors & other packaging people! I’d like to know your thoughts on PEP 803 – a proposal for stable ABI for Free-Threaded Builds. The main packaging-related points: Wheels tagged with the new ABI tag abi3…

---

## [PEP Idea: Extend spec of Callable to accept unpacked TypeDicts to specify keyword-only parameters](https://discuss.python.org/t/pep-idea-extend-spec-of-callable-to-accept-unpacked-typedicts-to-specify-keyword-only-parameters/96975)

<div class="topic-metadata">

**Author:** [@Daraan](https://discuss.python.org/u/Daraan)\
**Replies:** 49\
**Last updated:** [January 7, 2026, 11:26am UTC](https://discuss.python.org/t/pep-idea-extend-spec-of-callable-to-accept-unpacked-typedicts-to-specify-keyword-only-parameters/96975 "2026-01-07T11:26:10Z")

</div>

Currently the parameters described by Callable are considered positional-only. For more precise signatures we need to write a callback Protocol. Since PEP 692 TypedDicts can be used to type keyword parameters: def foo(\*…

---

## [PEP 257 return type update](https://discuss.python.org/t/pep-257-return-type-update/104421)

<div class="topic-metadata">

**Author:** [@gerardw](https://discuss.python.org/u/gerardw)\
**Replies:** 3\
**Last updated:** [October 23, 2025, 7:23pm UTC](https://discuss.python.org/t/pep-257-return-type-update/104421 "2025-10-23T19:23:54Z")

</div>

PEP 257 currently says: The one-line docstring should NOT be a “signature” reiterating the function/method parameters (which can be obtained by introspection). Don’t do:: def function(a, b): """function(a, b) -\>…

---

## [PEP 763: Limiting deletions on PyPI](https://discuss.python.org/t/pep-763-limiting-deletions-on-pypi/69487)

<div class="topic-metadata">

**Author:** [@woodruffw](https://discuss.python.org/u/woodruffw)\
**Replies:** 40\
**Last updated:** [September 29, 2025, 1:40pm UTC](https://discuss.python.org/t/pep-763-limiting-deletions-on-pypi/69487 "2025-09-29T13:40:33Z")

</div>

This is the discussion thread for PEP 763: Limiting deletions on PyPI PEP text: PEP 763 – Limiting deletions on PyPI | peps.python.org Previous discussions: Pre-PEP: Limiting deletions on PyPI Stop Allowing deleting …

---

## [How to find a PEP sponsor](https://discuss.python.org/t/how-to-find-a-pep-sponsor/97242)

<div class="topic-metadata">

**Author:** [@tanrbobanr](https://discuss.python.org/u/tanrbobanr)\
**Replies:** 1\
**Last updated:** [June 30, 2025, 10:22pm UTC](https://discuss.python.org/t/how-to-find-a-pep-sponsor/97242 "2025-06-30T22:22:38Z")

</div>

Hello all! When designing a new PEP, how does one go about finding a sponsor?

---

## [Proposal: Implicit self in Python 4.x (reduce boilerplate in instance methods)](https://discuss.python.org/t/proposal-implicit-self-in-python-4-x-reduce-boilerplate-in-instance-methods/96791)

<div class="topic-metadata">

**Author:** [@devdasher](https://discuss.python.org/u/devdasher)\
**Replies:** 4\
**Last updated:** [June 27, 2025, 4:14am UTC](https://discuss.python.org/t/proposal-implicit-self-in-python-4-x-reduce-boilerplate-in-instance-methods/96791 "2025-06-27T04:14:04Z")

</div>

Hi everyone, I’ve been exploring ways to reduce boilerplate in Python’s class syntax, and I would like to share a proposal for implicit self in instance methods, as a potential feature for Python 4.x. :glowing\_star: Id…

---

## [PEP idea: Support for Private Packages on PyPI using Existing Token System](https://discuss.python.org/t/pep-idea-support-for-private-packages-on-pypi-using-existing-token-system/90747)

<div class="topic-metadata">

**Author:** [@MilesONerd](https://discuss.python.org/u/MilesONerd)\
**Replies:** 6\
**Last updated:** [May 4, 2025, 10:23pm UTC](https://discuss.python.org/t/pep-idea-support-for-private-packages-on-pypi-using-existing-token-system/90747 "2025-05-04T22:23:45Z")

</div>

Hi everyone! I’m excited to share a draft proposal for a PEP, which aims to introduce native support for private packages on PyPI using the existing token-based authentication system. This PEP addresses a long-standing …

---

## [PEP 766: handling multiple indexes (Index Priority)](https://discuss.python.org/t/pep-766-handling-multiple-indexes-index-priority/71589)

<div class="topic-metadata">

**Author:** [@msarahan](https://discuss.python.org/u/msarahan)\
**Replies:** 22\
**Last updated:** [April 7, 2025, 2:38pm UTC](https://discuss.python.org/t/pep-766-handling-multiple-indexes-index-priority/71589 "2025-04-07T14:38:05Z")

</div>

UPDATE: This is PEP 766 – Explicit Priority Choices Among Multiple Indexes | peps.python.org Greetings Pythonistas. In discussions about how to extend the metadata that we can support, the topic of index priority came u…

---

## [PEP 11: Proposal to promote AArch64 platforms to Tier-1](https://discuss.python.org/t/pep-11-proposal-to-promote-aarch64-platforms-to-tier-1/44774)

<div class="topic-metadata">

**Author:** [@diegor](https://discuss.python.org/u/diegor)\
**Replies:** 30\
**Last updated:** [January 20, 2025, 3:08pm UTC](https://discuss.python.org/t/pep-11-proposal-to-promote-aarch64-platforms-to-tier-1/44774 "2025-01-20T15:08:33Z")

</div>

Hello CPython community! Since last year I’ve been active in the CPython community looking after Arm platforms. At EuroPython 2023 I gave a talk about “Python on Arm” and I highlighted two main takeaways: public benchma…

---

## [Sharing code in python without quirks](https://discuss.python.org/t/sharing-code-in-python-without-quirks/57066)

<div class="topic-metadata">

**Author:** [@rubmz](https://discuss.python.org/u/rubmz)\
**Replies:** 9\
**Last updated:** [January 1, 2025, 2:24pm UTC](https://discuss.python.org/t/sharing-code-in-python-without-quirks/57066 "2025-01-01T14:24:51Z")

</div>

Hi, Seems that there is a kind of a big annoying issue in python for many years, which I assume brings many people and many, many opinions… but is frankly very simple: In any other programming language when you want to…

---

## [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 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…

---

## [Type Signatures for extension modules (PEP draft)](https://discuss.python.org/t/type-signatures-for-extension-modules-pep-draft/43914)

<div class="topic-metadata">

**Author:** [@skirpichev](https://discuss.python.org/u/skirpichev)\
**Replies:** 22\
**Last updated:** [March 27, 2024, 5:01pm UTC](https://discuss.python.org/t/type-signatures-for-extension-modules-pep-draft/43914 "2024-03-27T17:01:26Z")

</div>

This pr slightly relaxes format requirements for text signatures in PyDoc\_STRVAR and adds support for return annotations in the \_\_text\_signature\_\_. Asking for review per suggestion in the devguide. Perhaps, related iss…

---

## [PEP 675 – Arbitrary Literal String Type](https://discuss.python.org/t/pep-675-arbitrary-literal-string-type/45775)

<div class="topic-metadata">

**Author:** [@Prometheus3375](https://discuss.python.org/u/Prometheus3375)\
**Replies:** 1\
**Last updated:** [February 14, 2024, 12:42am UTC](https://discuss.python.org/t/pep-675-arbitrary-literal-string-type/45775 "2024-02-14T00:42:57Z")

</div>

This PEP is already implemented in Python, however, I found some uncovered cases. This includes other literal values and their conversion to string. The only example provided about other literal types is the next: Oth…

---

## [Proposed update to PEP-11 on Unsupporting a platform (less draconian measures)](https://discuss.python.org/t/proposed-update-to-pep-11-on-unsupporting-a-platform-less-draconian-measures/44065)

<div class="topic-metadata">

**Author:** [@gpshead](https://discuss.python.org/u/gpshead)\
**Replies:** 12\
**Last updated:** [February 1, 2024, 7:29pm UTC](https://discuss.python.org/t/proposed-update-to-pep-11-on-unsupporting-a-platform-less-draconian-measures/44065 "2024-02-01T19:29:03Z")

</div>

When a platform loses Tier support status as defined in PEP-11 : Unsupporting platforms, the current text is rather draconian. It claims we must break the build and configure for said platform. This seems unreasonable. …

---

## [Clarification for PEP 604: is \`foo: int | None\` to replace all use of \`foo: Optional\[int\]\`](https://discuss.python.org/t/clarification-for-pep-604-is-foo-int-none-to-replace-all-use-of-foo-optional-int/26945)

<div class="topic-metadata">

**Author:** [@cjw296](https://discuss.python.org/u/cjw296)\
**Replies:** 43\
**Last updated:** [January 5, 2024, 5:51pm UTC](https://discuss.python.org/t/clarification-for-pep-604-is-foo-int-none-to-replace-all-use-of-foo-optional-int/26945 "2024-01-05T17:51:03Z")

</div>

The text of PEP 604 lacks clarity around the desired end state: All typing annotations should be moved to foo: int | None It’s a per-project preference that foo: Optional\[int\] can be used forever more I should point …

---

## [PEP 732: The Python Documentation Editorial Board](https://discuss.python.org/t/pep-732-the-python-documentation-editorial-board/36710)

<div class="topic-metadata">

**Author:** [@jojablonski](https://discuss.python.org/u/jojablonski)\
**Replies:** 8\
**Last updated:** [December 11, 2023, 2:39pm UTC](https://discuss.python.org/t/pep-732-the-python-documentation-editorial-board/36710 "2023-12-11T14:39:19Z")

</div>

Here’s a new PEP that proposes how the Python Documentation Editorial Board will work: Any feedback on this PEP would be appreciated.
