Creative Design & Branding
Python PEP Author
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python community. Covers all three PEP types (Standards Track, Informational, Process): choosing the right type, scaffolding a valid reStructuredText pep-NNNN file, filling each required section to the acceptance bar, linting the headers, and navigating the sponsor / submission / Steering Council review process. Trigger on \"write a PEP\", \"draft a PEP\", \"propose a Python feature\", \"create a Python Enhancement Proposal\", \"PEP template\", or when someone is preparing a proposal for the Python Discourse or python-dev. Use it even if the user only says \"PEP\" or doesn't mention reStructuredText — the headers, sections, and process are exactly what trips PEP authors up.
- Publisher / source
- pproenca/dot-skills (found on skills.sh)
- Upstream record
- pproenca/dot-skills
- Version
- Version 1
- Published
- Publication review
- Approved for publication
- Content fingerprint
3bec86b8ef6484be3eb061e6f088389f9ffae11e3cb237be61a9be2e5deb1e7a