Python 3.15.0b1
Python 3.15.0b1 베타 버전이 2026년 5월 7일에 공개되었으며, 주요 기능으로는 명시적 지연 임포트, frozendict 및 sentinel 내장 타입 추가, 고주파 통계 샘플링 프로파일러, 기본 UTF-8 인코딩 적용, JIT 컴파일러 성능 향상 등이 포함된다. 이번 베타는 기능 동결 단계로, 4차 베타까지 ABI 변경을 최소화하는 것이 목표이며, 프로덕션 환경에서는 3.15.0rc1 이후 버전 사용을 권장한다. 개발자들은 베타 기간 동안 테스트와 피드백 참여를 통해 안정적인 정식 출시를 지원할 수 있다.
Jack Schlossberg wants free PrEP for all — and for his cousin to stop undermining HIV care (exclusive)
https://fed.brid.gy/r/https://www.advocate.com/politics/national/jack-schlossberg-hiv-prevention
Python 3.15.0 beta 1 is here
Python 3.15.0 beta 1이 공개되어 주요 기능 동결과 함께 베타 테스트가 시작되었습니다. 이번 버전은 명시적 지연 임포트, frozendict 및 sentinel 내장 타입 추가, 새로운 프로파일링 패키지, JIT 컴파일러 성능 향상(최대 13% 속도 개선) 등 다양한 PEP 기능을 포함합니다. 또한 UTF-8 기본 인코딩 적용과 안정적인 ABI 지원이 강화되었으며, 윈도우 64비트 공식 바이너리는 꼬리 호출 인터프리터를 사용합니다. 개발자들은 베타 기간 동안 테스트와 피드백 참여가 권장되며, 프로덕션 환경에서는 RC 버전 이후 사용을 권고합니다.
PEP news!
PEP 831 – Frame Pointers Everywhere: Enabling System-Level Observability for Python
Accepted ✅
"After extensive deliberation the Steering Council has decided to accept PEP 831 (Frame Pointers Everywhere: yahdah yahdah), because it’s clearly the correct and necessary thing… although we wish the PEP and its title had been a lot shorter, given how much of an obvious decision it is. Congrats!"
Days until feature freeze: 4
After extensive deliberation the Steering Council has decided to accept PEP 831 (Frame Pointers Everywhere: yahdah yahdah), because it’s clearly the correct and necessary thing… although we wish the PEP and its title had been a lot shorter, given how much of an obvious decision it is. Congrats! (Pablo and Savannah, as PEP authors, were not involved in the decision process.)
PEP news!
PEP 788 – Protecting the C API from Interpreter Finalization: accepted
"Given that we have received no concerns from the C API WG or from the binding ecosystem, the SC is happy to accept the PEP."
https://discuss.python.org/t/pep-788-protecting-the-c-api-from-interpreter-finalization/104150/44
Given that we have received no concerns from the C API WG or from the binding ecosystem, the SC is happy to accept the PEP. Congratulations, @ZeroIntensity . Warm regards, Donghee on behalf of the Python Steering Council
PEP news!
PEP 829 – Package Startup Configuration Files: accepted
"The SC views PEP 829 as a sensible improvement to the interpreter layer, compatible with and not precluding future work in the installer and packaging standards space. We encourage contributors interested in that broader direction to consider proposing complementary standards. Accepting PEP 829 is not a statement that the interpreter layer is the end of this work."
https://discuss.python.org/t/pep-829-structured-startup-configuration-files/106789/112
The SC has discussed and is pleased to accept PEP 829 - Package Startup Configuration Files! The SC is comfortable with the three-year deprecation window as proposed. However, we request the following revisions to the text before the PEP lands: The current abstract buries the lede a bit. The first paragraph should highlight what is materially changing: <name>.start files with pkg.mod:callable syntax, a three-year .pth import-line deprecation, and retained path-extension .pth. The security imp...
PEP news:
PEP 661 – Sentinel Values: accepted
Originally created in 2021, and revived just in time for Python 3.15.
https://discuss.python.org/t/pep-661-sentinel-values/9126/337
PEP 806 – Mixed sync/async context managers with precise async marking: rejected
There's a high cost to adding new syntax. "The problem this PEP addresses, while genuine, does not in our view meet that bar."
On behalf of the Python Steering Council, I’m very happy to share that we have accepted PEP 661 for Python 3.15. Thank you @taleinat for creating the PEP and @Jelle for reviving it in time for 3.15. We especially appreciate how all of the SC’s earlier feedback was addressed nicely in the latest iteration of the PEP, resolving all of our previous concerns. Congrats!
Thomas Köhler
sayzard
Advocate.com [Unofficial]
Hugo van Kemenade
ImakeIcecream