Skip to content

PEP editor as a PEP sponsor #73

Closed
Closed

Description

@jorenham

For my PEP, @gvanrossum proposed that @JelleZijlstra would make an appropriate sponsor (see python/peps#2045
), as he has been helping me with the PEP since I first suggested the feature in python/typing#813. However, @JelleZijlstra is not a core developer, and I came to understand that this is not allowed. Would it be possible to make an exception to this rule?

Activity

  1. hugovk commented on Aug 9, 2021

    @hugovk
    Member

    PEP 1 says it's allowed with approval from the Steering Council, so you're in the right place!

    Ideally, a core developer sponsor is identified, but non-core sponsors may also be selected with the approval of the Steering Council.

    https://www.python.org/dev/peps/pep-0001/#submitting-a-pep

  2. JelleZijlstra commented on Aug 9, 2021

    @JelleZijlstra
    Member

    As background, I have been a core developer on https://github.com/python/typeshed/ and https://github.com/python/mypy for a few years, and more recently I have become a PEP editor and a triager on the CPython repo.

  3. brettcannon commented on Aug 9, 2021

    @brettcannon
    Member

    I thought we had a standing rule that PEP editors could sponsor PEPs since they obviously know how a PEP should be structured and handled?

  4. JelleZijlstra commented on Aug 9, 2021

    @JelleZijlstra
    Member

    Not in PEP 1 (Hugo linked the relevant text above), and if that rule is present somewhere else I'm not aware of it.

  5. changed the title [-]Non-core dev PEP sponsor[/-] [+]PEP editor as a PEP sponsor[/+] on Aug 11, 2021
  6. gvanrossum commented on Sep 7, 2021

    @gvanrossum
    Member

    Bumping this in the hope that it'll make the next SC agenda. Maybe before ruling about the general case (which might require a long discussion) the SC could quickly decide that it's okay for Jelle to sponsor the specific PEP we're talking about here? (That PEP is about adding +T and -T to indicate co-/contra-variance for type variables.)

  7. warsaw commented on Sep 7, 2021

    @warsaw
    Member

    Thanks @gvanrossum - I've pinged the SC to see if we can provide an answer before our next meeting.

  8. warsaw commented on Sep 8, 2021

    @warsaw
    Member

    @gvanrossum The SC is fine with @JelleZijlstra being the PEP Sponsor for this PEP.

  9. warsaw commented on Oct 18, 2021

    @warsaw
    Member

    There's nothing more to do for this ticket, closing.

  10. gvanrossum commented on Oct 18, 2021

    @gvanrossum
    Member

    So there's no ruling on the general case and no update to PEP 1 to bring it in line with Brett's recollection?

  11. warsaw commented on Oct 18, 2021

    @warsaw
    Member

    What exactly should PEP 1 be updated to say? Do you mind submitting a PR against PEP 1 to change the language?

  12. gvanrossum commented on Oct 18, 2021

    @gvanrossum
    Member
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions