Introduction

This YEP contains the index of all Yocto Enhancement Proposals, known as YEPs. YEP numbers are assigned by the YEP editors, and once assigned are never changed. The version control history of the YEP texts represent their historical record.

Topics

YEPs for specialist subjects are indexed by topic.

• Governance YEPs
• Packaging YEPs
• Release YEPs
• Typing YEPs

API

The YEPS API is a JSON file of metadata about all the published YEPs. Read more here.

Numerical Index

The numerical index contains a table of all YEPs, ordered by number.

Index by Category

YEP Types Key

• I — Informational: Non-normative YEP containing background, guidelines or other information relevant to the Python ecosystem
• P — Process: Normative YEP describing or proposing a change to a Python community process, workflow or governance
• S — Standards Track: Normative YEP with a new feature for Python, implementation change for CPython or interoperability standard for the ecosystem

More info in YEP 1.

YEP Status Key

• A — Accepted: Normative proposal accepted for implementation
• A — Active: Currently valid informational guidance, or an in-use process
• D — Deferred: Inactive draft that may be taken up again at a later time
• <No letter> — Draft: Proposal under active discussion and revision
• F — Final: Accepted and implementation complete, or no longer active
• P — Provisional: Provisionally accepted but additional feedback needed
• R — Rejected: Formally declined and will not be accepted
• S — Superseded: Replaced by another succeeding YEP
• W — Withdrawn: Removed from consideration by sponsor or authors

More info in YEP 1.

Authors/Owners