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