Mailman 3 February 2023 - Python-Dev

Contributing the Pyston jit?
by Kevin Modzelewski 27 Feb '23

27 Feb '23

Hello all, we on the Pyston team would like to propose the contribution of our JIT <https://github.com/pyston/pyston/blob/pyston_main/Python/aot_ceval_jit.c> into CPython main. We're interested in some initial feedback on this idea before putting in the work to rebase the jit to 3.12 for a PEP and more formal discussion. Our jit is designed to be simple and to generate code quickly, so we believe it's a good point on the design tradeoff curve for potential inclusion. The runtime behavior is intentionally kept almost completely the same as the interpreter, just lowered to machine code and with optimizations applied. Our jit currently targets Python 3.7-3.10, and on 3.8 it achieves a 10% speedup on macrobenchmarks (similar to 3.11). It's hard to estimate the potential speedup of our jit rebased onto 3.12 because there is overlap between what our jit does and the optimizations that have gone into the interpreter since 3.8, but there are several optimizations that would be additive with the current performance work: - Eliminating bytecode dispatch overhead - Mostly-eliminating stack management overhead - Reducing the number of reference count operations in the interpreter - Faster function calls, particularly of C functions - More specialization opportunities, both because a jit is not limited by bytecode limits, but also because it is able to do dynamic specializations that are not possible in an interpreter context There is also room for more optimizations -- in Pyston we've co-optimized the interpreter+jit combination such as by doing more extensive profiling in the interpreter. Our plan would be to submit an initial version that does not contain these optimizations in order to minimize the diff, and add them later. Our jit uses the DynASM assembler library (part of LuaJIT) to generate machine code. Our jit currently supports Mac and Linux, 64-bit ARM and x86_64. Now that we have two architectures supported, adding additional ones is not too much work. We think that our jit fits nicely in the technical roadmap of the Faster CPython project, but conflicts with their plan to build a new custom tracing jit. As mentioned, we'd love to get feedback about the overall appetite for including a jit in CPython! kmod

3 5

[RELEASE] Python 3.11.1, 3.10.9, 3.9.16, 3.8.16, 3.7.16, and 3.12.0 alpha 3 are now available
by Łukasz Langa 18 Feb '23

18 Feb '23

Greetings! We bring you a slew of releases this fine Saint Nicholas / Sinterklaas day. Six simultaneous releases has got to be some record. There’s one more record we broke this time, you’ll see below. In any case, updating is recommended due to security content: 3.7 - 3.12: gh-98739 <https://github.com/python/cpython/issues/98739>: Updated bundled libexpat to 2.5.0 to fix CVE-2022-43680 <https://nvd.nist.gov/vuln/detail/CVE-2022-43680> (heap use-after-free). 3.7 - 3.12: gh-98433 <https://github.com/python/cpython/issues/98433>: The IDNA codec decoder used on DNS hostnames by socket or asyncio related name resolution functions no longer involves a quadratic algorithm to fix CVE-2022-45061 <https://nvd.nist.gov/vuln/detail/CVE-2022-45061>. This prevents a potential CPU denial of service if an out-of-spec excessive length hostname involving bidirectional characters were decoded. Some protocols such as urllib http 3xx redirects potentially allow for an attacker to supply such a name. 3.7 - 3.12: gh-100001 <https://github.com/python/cpython/issues/100001>: python -m http.server no longer allows terminal control characters sent within a garbage request to be printed to the stderr server log. 3.8 - 3.12: gh-87604 <https://github.com/python/cpython/issues/87604>: Avoid publishing list of active per-interpreter audit hooks via the gc module. 3.9 - 3.10 (already released in 3.11+ before): gh-97514 <https://github.com/python/cpython/issues/97514>: On Linux the multiprocessing module returns to using filesystem backed unix domain sockets for communication with the forkserver process instead of the Linux abstract socket namespace. Only code that chooses to use the “forkserver” start method is affected. This prevents Linux CVE-2022-42919 <https://nvd.nist.gov/vuln/detail/CVE-2022-42919> (potential privilege escalation) as abstract sockets have no permissions and could allow any user on the system in the same network namespace (often the whole system) to inject code into the multiprocessing forkserver process. This was a potential privilege escalation. Filesystem based socket permissions restrict this to the forkserver process user as was the default in Python 3.8 and earlier. 3.7 - 3.10: gh-98517 <https://github.com/python/cpython/issues/98517>: Port XKCP’s fix for the buffer overflows in SHA-3 to fix CVE-2022-37454 <https://nvd.nist.gov/vuln/detail/CVE-2022-37454>. 3.7 - 3.9 (already released in 3.10+ before): gh-68966 <https://github.com/python/cpython/issues/68966>: The deprecated mailcap module now refuses to inject unsafe text (filenames, MIME types, parameters) into shell commands to address CVE-2015-20107 <https://nvd.nist.gov/vuln/detail/CVE-2015-20107>. Instead of using such text, it will warn and act as if a match was not found (or for test commands, as if the test failed). <https://discuss.python.org/t/python-3-11-1-3-10-9-3-9-16-3-8-16-3-7-16-and-…>Python 3.12.0 alpha 3 Get it here, read the change log, sing a GPT-3-generated Sinterklaas song: https://www.python.org/downloads/release/python-3120a3/ <https://www.python.org/downloads/release/python-3120a3/> 216 new commits since 3.12.0 alpha 2 last month. <https://discuss.python.org/t/python-3-11-1-3-10-9-3-9-16-3-8-16-3-7-16-and-…>Python 3.11.1 Get it here, see the change log, read the recipe for quark soup: https://www.python.org/downloads/release/python-3111/ <https://www.python.org/downloads/release/python-3111/> A whopping 495 new commits since 3.11.0. This is a massive increase of changes comparing to 3.10 at the same stage in the release cycle: there were “only” 339 commits between 3.10.0 and 3.10.1. <https://discuss.python.org/t/python-3-11-1-3-10-9-3-9-16-3-8-16-3-7-16-and-…>Python 3.10.9 Get it here, read the change log, see circular patterns: https://www.python.org/downloads/release/python-3109/ <https://www.python.org/downloads/release/python-3109/> 165 new commits. <https://discuss.python.org/t/python-3-11-1-3-10-9-3-9-16-3-8-16-3-7-16-and-…>Python 3.9.16 Get it here, read the change log, consider upgrading to a newer version: https://www.python.org/downloads/release/python-3916/ <https://www.python.org/downloads/release/python-3916/> Security-only release with no binaries. 10 commits. <https://discuss.python.org/t/python-3-11-1-3-10-9-3-9-16-3-8-16-3-7-16-and-…>Python 3.8.16 Get it here, see the change log, definitely upgrade to a newer version: https://www.python.org/downloads/release/python-3816/ <https://www.python.org/downloads/release/python-3816/> Security-only release with no binaries. 9 commits. <https://discuss.python.org/t/python-3-11-1-3-10-9-3-9-16-3-8-16-3-7-16-and-…>Python 3.7.16 Get it here, read the change log, check PEP 537 <https://peps.python.org/pep-0537/>to confirm EOL is coming to this version in June 2023: https://www.python.org/downloads/release/python-3716/ <https://www.python.org/downloads/release/python-3716/> Security-only release with no binaries. 8 commits. <https://discuss.python.org/t/python-3-11-1-3-10-9-3-9-16-3-8-16-3-7-16-and-…>We hope you enjoy the new releases! Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://www.python.org/psf/ <https://www.python.org/psf/> Your friendly release team, Ned Deily @nad <https://discuss.python.org/u/nad> Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower> Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal> Łukasz Langa @ambv <https://discuss.python.org/u/ambv> Thomas Wouters @thomas <https://discuss.python.org/u/thomas>

3 3

[RELEASE] Python 3.11.2, Python 3.10.10 and 3.12.0 alpha 5 are available
by Pablo Galindo Salgado 08 Feb '23

08 Feb '23

Hi everyone, I am happy to report that after solving some last-time problems we have a bunch of fresh releases for you: ### Python 3.12.0 alpha 5 Check the new alpha of 3.12 with some Star Trek vibes: https://www.python.org/downloads/release/python-3120a5/ 210 new commits since 3.12.0a4 last month ### Python 3.11.2 A shipment of bugfixes and security releases for the newest Python! https://www.python.org/downloads/release/python-3112/ 194 new commits since 3.11.1 ### Python 3.10.10 Your trusty Python3.10 just got more stable and secure! https://www.python.org/downloads/release/python-31010/ 131 new commits since 3.10.9 ## We hope you enjoy the new releases! Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://www.python.org/psf/ Your friendly release team, Ned Deily @nad Steve Dower @steve.dower Pablo Galindo Salgado @pablogsal Łukasz Langa @ambv Thomas Wouters @thomas

1 0

Python Language Summit at PyCon US 2023 in Salt Lake City
by Łukasz Langa 07 Feb '23

07 Feb '23

We’re excited to announce that the signups for the Python Language Summit at PyCon US 2023 are now open. Full details at: https://us.pycon.org/2023/events/language-summit/ <https://us.pycon.org/2023/events/language-summit/> Just like in 2022, we are doing the Summit as an in-person event. We will be following the health and safety guidelines <https://us.pycon.org/2023/about/health-safety-guidelines/> of the wider conference. <https://discuss.python.org/t/python-language-summit-at-pycon-us-2023-in-sal…>TL;DR When: Wednesday, April 19, 2023 at 10:00am Where: Salt Palace Convention Center, room TBD Sign up to attend: https://forms.gle/YnWL1Hts6zDtdSgn7 <https://forms.gle/YnWL1Hts6zDtdSgn7> (closes March 5th, 2023 AoE) <https://discuss.python.org/t/python-language-summit-at-pycon-us-2023-in-sal…>Who can attend We welcome Python core developers and triage team members, active contributors to CPython and alternative Python implementations, and other community members with a topic to discuss with core developers. <https://discuss.python.org/t/python-language-summit-at-pycon-us-2023-in-sal…>Who can propose a discussion topic If you have discussion items; seeking consensus; awaiting decision on a PEP; needing help with your core dev work; or have specific questions that need answers from core developers, please submit a proposal. According to feedback, our audience prefers more discussions and shorter talks. In your proposal, please include the following: why is this topic relevant to the core developers; what is needed from core developers out of this topic. <https://discuss.python.org/t/python-language-summit-at-pycon-us-2023-in-sal…>How can I learn what’s happening at the event? Like in 2022, this year’s event will be covered by @AlexWaygood <https://discuss.python.org/u/alexwaygood>. A detailed summary of the event will be published on the Python Software Foundation Blog <https://pyfound.blogspot.com/>. <https://discuss.python.org/t/python-language-summit-at-pycon-us-2023-in-sal…>Is this event recorded? Can I watch the live stream? No, there will be no recording and no live stream available. If you’d like to participate in discussions, please sign up to attend. If you’d like to listen in, please wait for Alex’s blog posts after the Summit. <https://discuss.python.org/t/python-language-summit-at-pycon-us-2023-in-sal…>We hope you have a great event! Your Language Summit cat herding team, @ambv <https://discuss.python.org/u/ambv> & @Senthil <https://discuss.python.org/u/senthil>

1 0

PEP 638: Syntactic macros
by Mark Shannon 05 Feb '23

05 Feb '23

Hi everyone, I've submitted my PEP on syntactic macros as PEP 638. https://www.python.org/dev/peps/pep-0638/ All comments and suggestions are welcome. Cheers, Mark

16 25

Python-Dev February 2023