> >
> > class SubFoo(Foo):
> > def __init__(self, *args, **kw):
> > Foo(self, *args, **kw)
> > ...
Guido:
> I like the idea, but it would mean a major reworking of the grammar
> and the parser. Can I persuade you to keep this on ice until 2.0?
What exactly would the semantics be? While I hate the apply() loops you have
to jump through nowadays to get this behaviour I don't funny understand how
this would work in general (as opposed to in this case). For instance, would
Foo(self, 12, *args, **kw)
be allowed? And
Foo(self, *args, x=12, **kw)
?
--
Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++
Jack.Jansen at oratrix.com | ++++ if you agree copy these lines to your sig ++++
www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4