Python Enhancement Proposal 略して PEP
PythonのドキュメントやGuidoのブログを読んでるとPEP PEPと登場する。なんだこれはと思ったので調べたらそういうことらしい。PEPとは Python Emhancement Proposal ：日本語だと。「こんなの作って、Pythonをより良くしようぜ！」 小難しく訳すと、「Python基本改良方針候補集」かな。
- PythonのPEP集(たぶん日本語訳されることはないだろう)
PEPに並んでる。PI,I,Sの記号はたぶんこれのこと。
PEP Types
There are three kinds of PEP:
- A Standards Track PEP describes a new feature or implementation for Python.
- An Informational PEP describes a Python design issue, or provides general guidelines or information to the Python community, but does not propose a new feature. Informational PEPs do not necessarily represent a Python community consensus or recommendation, so users and implementors are free to ignore Informational PEPs or follow their advice.
- 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 release schedules, procedures, guidelines, changes to the decision-making process, and changes to the tools or environment used in Python development.
ガイドラインくらいは邦訳があっても良いよね。
