PEP 520: Resolve dangling hyphens (#3358)
This commit is contained in:
parent
ee2f31e163
commit
eaa4742315
12
pep-0520.txt
12
pep-0520.txt
|
@ -37,8 +37,8 @@ This allows introspection of the original definition order, e.g. by
|
||||||
class decorators.
|
class decorators.
|
||||||
|
|
||||||
Additionally, this PEP requires that the default class definition
|
Additionally, this PEP requires that the default class definition
|
||||||
namespace be ordered (e.g. ``OrderedDict``) by default. The long-
|
namespace be ordered (e.g. ``OrderedDict``) by default. The
|
||||||
lived class namespace (``__dict__``) will remain a ``dict``.
|
long-lived class namespace (``__dict__``) will remain a ``dict``.
|
||||||
|
|
||||||
|
|
||||||
Motivation
|
Motivation
|
||||||
|
@ -185,10 +185,10 @@ the well-worn precedent found in Python. Per Guido::
|
||||||
|
|
||||||
Also, note that a writeable ``__definition_order__`` allows dynamically
|
Also, note that a writeable ``__definition_order__`` allows dynamically
|
||||||
created classes (e.g. by Cython) to still have ``__definition_order__``
|
created classes (e.g. by Cython) to still have ``__definition_order__``
|
||||||
properly set. That could certainly be handled through specific class-
|
properly set. That could certainly be handled through specific
|
||||||
creation tools, such as ``type()`` or the C-API, without the need to
|
class-creation tools, such as ``type()`` or the C-API, without the need
|
||||||
lose the semantics of a read-only attribute. However, with a writeable
|
to lose the semantics of a read-only attribute. However, with a
|
||||||
attribute it's a moot point.
|
writeable attribute it's a moot point.
|
||||||
|
|
||||||
|
|
||||||
Why not "__attribute_order__"?
|
Why not "__attribute_order__"?
|
||||||
|
|
Loading…
Reference in New Issue