Skip to content

Process of proposing (new) specifications may not sufficiently clearly explained #764

Open

Description

@pradyunsg

From https://discuss.python.org/t/adding-a-default-extra-require-environment/4898/48?u=pradyunsg

I found this: https://www.pypa.io/en/latest/specifications/#proposing-new-specifications but honestly it’s quite confusing and not really helpful.

I try to understand:

  • How to obtain a PEP number ?
  • Where should I go to open the PEP ?
  • Is the PR to " Python Packaging User Guide repository" the PEP itself ? Or it’s a completely different process and shall be done once we have reached consensus in the PEP ?
  • Is there a template I can follow ?

I feel that these are all legitimate questions about the process that we don't clarify well enough, and we should possibly clarify each of these points in/near the "Proposing new specifications" section.

Activity

  1. changed the title [-]Process of suggesting changes to the specifications may not sufficiently clearly explained[/-] [+]Process of proposing (new) specifications may not sufficiently clearly explained[/+] on Aug 19, 2020
  2. pradyunsg commented on Aug 22, 2020

    @pradyunsg
    MemberAuthor

    pypa/packaging-problems#367 (comment)

    Another instance of this. :)

  3. hugovk commented on Aug 22, 2020

    @hugovk
    Contributor

    Are some of these are answered in PEP 1?

    For example, "Once approved [not the same as accepted], they [the PEP editors] will assign your PEP a number".

    If so, PEP 1 may need updating for packaging PEPs.

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