Skip to content

PEP 520: Resolve dangling hyphens #3358

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 1, 2023
Merged

PEP 520: Resolve dangling hyphens #3358

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions pep-0520.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,8 +37,8 @@ This allows introspection of the original definition order, e.g. by
class decorators.

Additionally, this PEP requires that the default class definition
namespace be ordered (e.g. ``OrderedDict``) by default. The long-
lived class namespace (``__dict__``) will remain a ``dict``.
namespace be ordered (e.g. ``OrderedDict``) by default. The
long-lived class namespace (``__dict__``) will remain a ``dict``.


Motivation
Expand Down Expand Up @@ -185,10 +185,10 @@ the well-worn precedent found in Python. Per Guido::

Also, note that a writeable ``__definition_order__`` allows dynamically
created classes (e.g. by Cython) to still have ``__definition_order__``
properly set. That could certainly be handled through specific class-
creation tools, such as ``type()`` or the C-API, without the need to
lose the semantics of a read-only attribute. However, with a writeable
attribute it's a moot point.
properly set. That could certainly be handled through specific
class-creation tools, such as ``type()`` or the C-API, without the need
to lose the semantics of a read-only attribute. However, with a
writeable attribute it's a moot point.


Why not "__attribute_order__"?
Expand Down