I&#x27;m relatively new to Python but one of the things I love most about the community is the easily accessible PEPs...I know Ruby has mailing lists and discussion groups where changes to the language are hashed out...but I&#x27;ve never come across anything that resembles PEP, a well-organized list of articles that aren&#x27;t just proposals, but well-edited documents that are a pleasure to read while going in-depth into the reasoning behind the proposal, the ensuing debate, and how&#x2F;when&#x2F;and why action was taken. I&#x27;ve never better understood a language better than I do Python.<p>As an example, one of my recent favorites is PEP 495 Local Time Disambiguation [0] -- a feature which has been approved for 3.6. I can&#x27;t summarize it capably, but it covers a topic about time that I hadn&#x27;t even thought about, in a very readable yet thorough fashion. I was reminded of it when reading the OP, because both PEPS involve a seemingly inexplicable naming issue that ends up having a perfectly rational explanation -- when you think through the details.<p>In PEP 495, which adds an attribute named `fold` to datetime objects, there&#x27;s debate about whether `fold` is the right term (or rather, why not have the attribute&#x27;s name be more closely tied to &quot;daylight savings time&quot;)...and the explanation, which covers past examples of confusion with DST, while anticipating compatibility issues with pre 3.6 datetime implementation, is perfectly convincing, as common sense as something can be regarding an esoteric topic.<p>[0] <a href="https:&#x2F;&#x2F;www.python.org&#x2F;dev&#x2F;peps&#x2F;pep-0495&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.python.org&#x2F;dev&#x2F;peps&#x2F;pep-0495&#x2F;</a>