PEP.py

########## PEP ##########


# PEPs are primarily addressed to Python developers and members of the Python community
# They are maintained as text files in a repository, and can be accessed online at https://www.python.org/dev/peps/
# ANYONE can propose a PEP
# PEP formats, templates, and the submission process (including reporting bugs and submitting updates) as well as the 
# subsequent stages: review, resolution, and maintenance, are all described in detail within PEP 1 
# ==> PEP Purpose and Guidelines 


### PEP 0 - Index of Python Enhancement Proposals (PEPs)
# https://peps.python.org/pep-0000/



### PEP 1 – PEP Purpose and Guidelines

# 3 different types of PEPs:
#   Standards Track PEPs ==> describe new language features and implementations
#   Informational PEPs   ==> describe Python design issues, as well as provide guidelines and information to the Python community
#   Process PEPs         ==> describe various processes that revolve around Python = propose changes, provide recommendations, specify certain procedures

# Last but not least, PEP 1 defines:
#   Python’s Steering Council ==> a five-person committee and the final authorities who accept or reject PEPs
#   Python’s Core Developers  ==> the group of volunteers who manage Python, and
#   Python’s BDFL             ==> Guido van Rossum, the original creator of Python, who served as the project’s Benevolent Dictator For Life until 2018, when he resigned from the decision-making process



# PEP 8 – Style Guide for Python Code, which gives conventions and presents best practices for Python coding



# PEP 20 – The Zen of Python, which presents a list of principles for Python’s design



# PEP 257 – Docstring Conventions, which provides guidelines for conventions and semantics associated with Python docstrings