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

PEP 367: Resolve dangling hyphens (#3349)

This commit is contained in:
Adam Turner 2023-09-01 19:41:38 +01:00 committed by GitHub
parent 043306b1f7
commit 3bbf470f3f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
pep-0367.txt
View File

@ -122,10 +122,10 @@ Should ``super`` actually become a keyword?
With this proposal, ``super`` would become a keyword to the same extent that With this proposal, ``super`` would become a keyword to the same extent that
``None`` is a keyword. It is possible that further restricting the ``super`` ``None`` is a keyword. It is possible that further restricting the ``super``
name may simplify implementation, however some are against the actual keyword- name may simplify implementation, however some are against the actual
ization of super. The simplest solution is often the correct solution and the keyword-ization of super. The simplest solution is often the correct solution
simplest solution may well not be adding additional keywords to the language and the simplest solution may well not be adding additional keywords to the
when they are not needed. Still, it may solve other open issues. language when they are not needed. Still, it may solve other open issues.
Closed Issues Closed Issues
@ -513,10 +513,10 @@ super(self, \*args) or __super__(self, \*args)
This solution only solves the problem of the type indication, does not handle This solution only solves the problem of the type indication, does not handle
differently named super methods, and is explicit about the name of the differently named super methods, and is explicit about the name of the
instance. It is less flexible without being able to enacted on other method instance. It is less flexible without being able to enacted on other method
names, in cases where that is needed. One use case this fails is where a base- names, in cases where that is needed. One use case this fails is where a
class has a factory classmethod and a subclass has two factory classmethods, base-class has a factory classmethod and a subclass has two factory
both of which needing to properly make super calls to the one in the base- classmethods, both of which needing to properly make super calls to the one
class. in the base-class.
super.foo(self, \*args) super.foo(self, \*args)
----------------------- -----------------------