PEP 602: Mark as Active Process

[hugovk]

Helps #2872.

PEP 602 is a Process PEP rather than Informational or Standards Track:

A Process PEP describes a process surrounding Python, or proposes a change to (or an event in) a process. Process PEPs are like Standards Track PEPs but apply to areas other than the Python language itself. They may propose an implementation, but not to Python’s codebase; they often require community consensus; unlike Informational PEPs, they are more than recommendations, and users are typically not free to ignore them. Examples include procedures, guidelines, changes to the decision-making process, and changes to the tools or environment used in Python development. Any meta-PEP is also considered a Process PEP.

And as such won't ever be be "fully implemented" and marked as Final.

Instead, it should be set to Active:

Some Informational and Process PEPs may also have a status of “Active” if they are never meant to be completed. E.g. PEP 1 (this PEP).

Also remove some redundant headers/emacs metadata.

---

📚 Documentation preview 📚: https://pep-previews--3736.org.readthedocs.build/