From 2e9b04a22aa247c0f5a7543607dd0002a07f05f2 Mon Sep 17 00:00:00 2001 From: Nick Coghlan Date: Wed, 6 Jun 2012 21:44:01 +1000 Subject: [PATCH] Fix numbered bullet points --- pep-0422.txt | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/pep-0422.txt b/pep-0422.txt index 1c22a4bb8..8cd370ee2 100644 --- a/pep-0422.txt +++ b/pep-0422.txt @@ -79,16 +79,16 @@ Proposal This PEP proposes that a mechanism be added to Python 3 that meets the following criteria: -# Restores the ability for class namespaces to have some influence on the - class creation process (above and beyond populating the namespace itself), - but potentially without the full flexibility of the Python 2 style - ``__metaclass__`` hook -# Integrates nicely with class inheritance structures (including mixins and - multiple inheritance) -# Integrates nicely with the implicit ``__class__`` reference and - zero-argument ``super()`` syntax introduced by PEP 3135 -# Can be added to an existing base class without a significant risk of - introducing backwards compatibility problems +1. Restores the ability for class namespaces to have some influence on the + class creation process (above and beyond populating the namespace itself), + but potentially without the full flexibility of the Python 2 style + ``__metaclass__`` hook +2. Integrates nicely with class inheritance structures (including mixins and + multiple inheritance) +3. Integrates nicely with the implicit ``__class__`` reference and + zero-argument ``super()`` syntax introduced by PEP 3135 +4. Can be added to an existing base class without a significant risk of + introducing backwards compatibility problems One mechanism that would achieve this goal is to add a new class initialisation hook, modelled directly on the existing instance