Page 2, found in 20 ms

  1. peps.python.orghttps://peps.python.org › pep-0101
    More about peps.python.org
    PEP 101 – Doing Python Releases 101 | peps.python.org

    … the CPython repository on GitHub, create a release branch within it (called the “release clone” from now on). You can use the same GitHub fork you use for CPython development. Using the …

    0 points
  2. peps.python.orghttps://peps.python.org › pep-0549
    More about peps.python.org
    PEP 549 – Instance Descriptors | peps.python.org

    … is under development at GitHub [github] . Acknowledgements Armin Rigo essentially proposed this mechanism when presented with the idea of “module properties”, and educated the author both on the complexities of the problem …

    0 points
  3. peps.python.orghttps://peps.python.org › pep-0761
    More about peps.python.org
    PEP 761 – Deprecating PGP signatures for CPython artifacts | peps.python.org

    … PyPI, NPM, Homebrew, and GitHub, among other ecosystems. This PEP proposes to move CPython to using Sigstore exclusively for signing artifacts through a deprecation and eventual discontinuance of providing PGP signatures with …

    0 points
  4. peps.python.orghttps://peps.python.org › pep-8002
    More about peps.python.org
    PEP 8002 – Open Source Governance Survey | peps.python.org

    … e-mails for all GitHub activity is not popular. There are planning and triage meetings open to the public happening on IRC and Discord. They are not very popular because most of …

    0 points
  5. peps.python.orghttps://peps.python.org › pep-0753
    More about peps.python.org
    PEP 753 – Uniform project URLs in core metadata | peps.python.org

    PEP 753 – Uniform project URLs in core metadata PEP 753 – Uniform project URLs in core metadata Author : William Woodruff <william at yossarian.net>, Facundo Tuesca <facundo.tuesca at trailofbits.com> Sponsor : Barry Warsaw <barry at …

    0 points
  6. peps.python.orghttps://peps.python.org › pep-0774
    More about peps.python.org
    PEP 774 – Removing the LLVM requirement for JIT builds | peps.python.org

    … also took place on GitHub . As part of that discussion, there was also a clear appetite for removing the LLVM requirement for JIT builds in preparation for shipping the JIT off by …

    0 points
  7. peps.python.orghttps://peps.python.org › pep-8012
    More about peps.python.org
    PEP 8012 – The Community Governance Model | peps.python.org

    PEP 8012 – The Community Governance Model PEP 8012 – The Community Governance Model Author : Łukasz Langa <lukasz at python.org> Status : Rejected Type : Informational Topic : Governance Created : 03-Oct-2018 Table of Contents PEP …

    0 points
  8. peps.python.orghttps://peps.python.org › pep-0507
    More about peps.python.org
    PEP 507 – Migrate CPython to Git and GitLab | peps.python.org

    … open source alternative to GitHub and omits the proposal to run Phabricator. As with PEP 481 , this particular PEP is offered as an alternative to PEP 474 and PEP 462 . Rationale CPython …

    0 points
  9. peps.python.orghttps://peps.python.org › pep-0730
    More about peps.python.org
    PEP 730 – Adding iOS as a supported platform | peps.python.org

    PEP 730 – Adding iOS as a supported platform PEP 730 – Adding iOS as a supported platform Author : Russell Keith-Magee <russell at keith-magee.com> Sponsor : Ned Deily <nad at python.org> Discussions-To …

    0 points
  10. peps.python.orghttps://peps.python.org › pep-0541
    More about peps.python.org
    PEP 541 – Package Index Name Retention | peps.python.org

    … 3] , NPM [4] , and GitHub [5] will be investigated as prior art in this field. Rationale Given that package names on the Index are sharing a single flat namespace, a unique name …

    0 points

Search for “github site:peps.python.org” on Google, or add !ddg, !w and other shortcuts to any search.