Search results for “site:discuss.python.org”
Page 6 of about
67 results
d
discuss.python.org
t › interpreters-vs-concurrent-interpreters › 95980
Hi all (and especially the Steering Council and our 3.14 RM), The new module from PEP 734 is happily part of 3.14 now, the culmination of the primary phase of a project I started over a decade ago. I’m excited at the p…
d
discuss.python.org
t › a-massive-pep-649-update-with-some-major-course-corrections › 25672
Howdy howdy. I’ve been doing a lot more thinking about PEP 649 since the last discussion topic from a few weeks back. I propose to revise some important details, detailed below. One proviso before I begin. It’s a g…
d
discuss.python.org
t › pep-649-deferred-evaluation-of-annotations-tentatively-accepted › 21331
The Python Steering Council is tentatively accepting @larry 's PEP-649: Deferred Evaluation Of Annotations Using Descriptors. (related GH PSC agenda item issue) Why tentatively? What does that even mean? It means we th…
d
discuss.python.org
t › pre-pep-discussion-stop-providing-gpg-signatures-for-cpython-artifacts › 65058
Hey all, getting the ball rolling on this discussion. My proposal is that for Python 3.14 and onwards we stop providing GPG signatures for artifacts, instead relying entirely on Sigstore bundles to provide authenticity. …
d
discuss.python.org
t › pep-734-multiple-interpreters-in-the-stdlib › 41147 › 36
PEP 734 is the new proposal I’m introducing to replace PEP 554. The new PEP is available online: https://peps.python.org/pep-0734/. I’ve also included the text at the bottom of this post. Why a new PEP? PEP 554 was c…
d
discuss.python.org
t › python-3-11-5-3-10-13-3-9-18-and-3-8-18-is-now-available › 32254 › 1
There’s security content in the releases, let’s dive right in. gh-108310: Fixed an issue where instances of ssl.SSLSocket were vulnerable to a bypass of the TLS handshake and included protections (like certificate veri…
d
discuss.python.org
t › pep-779-criteria-for-supported-status-for-free-threaded-python › 84319 › 123
As you may remember, PEP 703 (Making the Global Interpreter Lock Optional in CPython) was accepted for Python 3.13, as an explicitly experimental feature. The acceptance by the SC proposed several phases to flesh out the…
d
discuss.python.org
t › pep-741-python-configuration-c-api-second-version › 45403 › 27
Hi, I wrote a major update of my PEP 741 “Python Configuration C API (second version)” to address most, if not all, requests in the previous discussion. => Read the updated PEP 741 <= See the Commit of the PEP 741 upd…
d
discuss.python.org
t › fr-allow-private-runtime-config-to-enable-extending-without-breaking-the-pyconfig-abi › 18004 › 34
Problem statement We need the ability to extend the configuration of the Python runtime within patch releases where we cannot change public structures and thus break a releases ABI. We don’t do this often, but security …
d
discuss.python.org
t › pre-pep-discussion-stop-providing-gpg-signatures-for-cpython-artifacts › 65058 › 9
Hey all, getting the ball rolling on this discussion. My proposal is that for Python 3.14 and onwards we stop providing GPG signatures for artifacts, instead relying entirely on Sigstore bundles to provide authenticity. …
Try “site:discuss.python.org” on:
Marginalia ·
Mojeek ·
Wiby ·
DuckDuckGo ·
Bing ·
Google ·
Wikipedia ·
Internet Archive