home.social

#pep — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pep, aggregated by home.social.

  1. 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!"

    discuss.python.org/t/pep-831-f

    Days until feature freeze: 4

    #Python #Python315 #PEP831 #PEP

  2. 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!"

    discuss.python.org/t/pep-831-f

    Days until feature freeze: 4

    #Python #Python315 #PEP831 #PEP

  3. 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!"

    discuss.python.org/t/pep-831-f

    Days until feature freeze: 4

    #Python #Python315 #PEP831 #PEP

  4. 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!"

    discuss.python.org/t/pep-831-f

    Days until feature freeze: 4

    #Python #Python315 #PEP831 #PEP

  5. 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!"

    discuss.python.org/t/pep-831-f

    Days until feature freeze: 4

    #Python #Python315 #PEP831 #PEP

  6. 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."

    discuss.python.org/t/pep-788-p

    #Python #PEP788 #Python315 #PEP #PEPs

  7. 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."

    discuss.python.org/t/pep-788-p

    #Python #PEP788 #Python315 #PEP #PEPs

  8. 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."

    discuss.python.org/t/pep-788-p

    #Python #PEP788 #Python315 #PEP #PEPs

  9. 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."

    discuss.python.org/t/pep-788-p

    #Python #PEP788 #Python315 #PEP #PEPs

  10. 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."

    discuss.python.org/t/pep-788-p

    #Python #PEP788 #Python315 #PEP #PEPs

  11. 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."

    discuss.python.org/t/pep-829-s

    #Python #PEP829 #Python315 #PEP #PEPs

  12. 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."

    discuss.python.org/t/pep-829-s

    #Python #PEP829 #Python315 #PEP #PEPs

  13. 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."

    discuss.python.org/t/pep-829-s

    #Python #PEP829 #Python315 #PEP #PEPs

  14. 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."

    discuss.python.org/t/pep-829-s

    #Python #PEP829 #Python315 #PEP #PEPs

  15. 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."

    discuss.python.org/t/pep-829-s

    #Python #PEP829 #Python315 #PEP #PEPs

  16. PEP news:

    PEP 661 – Sentinel Values: accepted

    Originally created in 2021, and revived just in time for Python 3.15.

    discuss.python.org/t/pep-661-s

    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."

    discuss.python.org/t/pep-806-m

    #Python #PEP661 #PEP806 #Python315 #PEP #PEPs

  17. PEP news:

    PEP 661 – Sentinel Values: accepted

    Originally created in 2021, and revived just in time for Python 3.15.

    discuss.python.org/t/pep-661-s

    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."

    discuss.python.org/t/pep-806-m

    #Python #PEP661 #PEP806 #Python315 #PEP #PEPs

  18. PEP news:

    PEP 661 – Sentinel Values: accepted

    Originally created in 2021, and revived just in time for Python 3.15.

    discuss.python.org/t/pep-661-s

    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."

    discuss.python.org/t/pep-806-m

    #Python #PEP661 #PEP806 #Python315 #PEP #PEPs

  19. PEP news:

    PEP 661 – Sentinel Values: accepted

    Originally created in 2021, and revived just in time for Python 3.15.

    discuss.python.org/t/pep-661-s

    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."

    discuss.python.org/t/pep-806-m

    #Python #PEP661 #PEP806 #Python315 #PEP #PEPs

  20. PEP news:

    PEP 661 – Sentinel Values: accepted

    Originally created in 2021, and revived just in time for Python 3.15.

    discuss.python.org/t/pep-661-s

    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."

    discuss.python.org/t/pep-806-m

    #Python #PEP661 #PEP806 #Python315 #PEP #PEPs