iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix numbered bullet points

This commit is contained in:
Nick Coghlan 2012-06-06 21:44:01 +10:00
parent 7bac3da1c4
commit 2e9b04a22a
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0422.txt
View File

@ -79,15 +79,15 @@ Proposal
This PEP proposes that a mechanism be added to Python 3 that meets the This PEP proposes that a mechanism be added to Python 3 that meets the
following criteria: following criteria:
# Restores the ability for class namespaces to have some influence on the 1. Restores the ability for class namespaces to have some influence on the
class creation process (above and beyond populating the namespace itself), class creation process (above and beyond populating the namespace itself),
but potentially without the full flexibility of the Python 2 style but potentially without the full flexibility of the Python 2 style
``__metaclass__`` hook ``__metaclass__`` hook
# Integrates nicely with class inheritance structures (including mixins and 2. Integrates nicely with class inheritance structures (including mixins and
multiple inheritance) multiple inheritance)
# Integrates nicely with the implicit ``__class__`` reference and 3. Integrates nicely with the implicit ``__class__`` reference and
zero-argument ``super()`` syntax introduced by PEP 3135 zero-argument ``super()`` syntax introduced by PEP 3135
# Can be added to an existing base class without a significant risk of 4. Can be added to an existing base class without a significant risk of
introducing backwards compatibility problems introducing backwards compatibility problems
One mechanism that would achieve this goal is to add a new class One mechanism that would achieve this goal is to add a new class