You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/intro/community.rst
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,3 +6,34 @@ BDFL
6
6
7
7
Python Software Foundation
8
8
--------------------------
9
+
10
+
11
+
PEPs
12
+
----
13
+
14
+
PEPs are *Python Enhancement Proposals*. They are define change to Python itself, or the standards around it.
15
+
16
+
There are three different types of PEPs (as defined by `PEP1 <http://www.python.org/dev/peps/pep-0001/>`_):
17
+
18
+
**Standards**
19
+
Describes a new feature or implementation.
20
+
21
+
**Informational**
22
+
Describes a design issue, general guidelines, or information to the community.
23
+
24
+
**Process**
25
+
Describes a process related to Python.
26
+
27
+
28
+
There are a few PEPs that could be considered required reading:
29
+
30
+
- `PEP8 <http://www.python.org/dev/peps/pep-0008/>`_: The Python Style Guide.
31
+
32
+
- `PEP20 <http://www.python.org/dev/peps/pep-0020/>`_: The Zen of Python. A list of 19 statements that briefly explain the philosophy behind Python.
33
+
34
+
- `PEP257 <http://www.python.org/dev/peps/pep-0257/>`_: Docstring Conventions. Gives guidelines for semantics and conventions associated with Python docstrings.
35
+
36
+
37
+
PEPs are peer-reviewed and accepted/rejected after much discussion. Anyone can write and submit a PEP for review.
0 commit comments