Just tell me how to do it! Please!

[rating: intermediate]

Ever heard of a “Request For Comments” document (RFC)? They are used by the IETF and other standards groups for people to participate in evolving standards.

Python as a language has a similar structure for submitting, debating & accepting proposals from people interested in evolving the Python language itself. The basis of this process are the Python Enhancement Proposals (PEP).

https://peps.python.org/

Naturally, PEP-0 is the index of all the PEP’s in “the system”.

Once you start getting beyond the basics of learning Python, then it quickly becomes useful to understand how the language is evolving, & how the community is thinking about potential changes to the language & its ecosystem of libraries & other capabilities.

In practice I’ve found that there’s a handful of PEP’s that are exceptionally useful on a regular basis, or just as background to keep in mind while developing Python applications. The rest are of interest if you really want to dive into some specific aspect of the Python ecosystem & perhaps contribute.

Go for it if that’s your thing!

Here’s my short list of the most useful PEP’s:

• PEP-8 Style Guide for Python

• PEP-440 Version Identification & Dependency Specification

• PEP-503 Simple repository API (for PyPI-like package repositories)

• PEP-508 Dependency specification for Python Software Packages

A few well known PEPs such as PEP-440 have been migrated out of the PEP system to other formal specifications:

PS What PEP’s have you found have daily use?

Python documentation:

https://peps.python.org/

I'm Russell 🐿️. A long time engineer discovering new life as a first-time solopreneur.

I build software delivery systems using Docker & Python automation that increase speed & reduce errors - saving money & improving profitability.