> This PEP is now accepted for inclusion in Python 3.6. Martin,
> congratulations!
Thank you very much! What a great news!
Greetings
Martin
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscrib
On 07/17/2016 09:57 AM, Guido van Rossum wrote:
This PEP is now accepted for inclusion in Python 3.6. Martin,
congratulations!
Congratulations, Martin!
I'm looking forward to this feature. :)
--
~Ethan~
___
Python-Dev mailing list
Python-Dev@pytho
So, for __qualname__, should we just update the docs to make this the
law? If that's your recommendation, I'm fine with it, and you can
submit a doc patch.
On Sun, Jul 17, 2016 at 10:01 AM, Martin Teichmann
wrote:
> Hi,
>
> so I did quite some research on this topic. And what I found out is
> tha
Hi,
so I did quite some research on this topic. And what I found out is
that __qualname__ needs to exist in the namespace. Not necessarily
because it should be used, but because it may be modified.
The story goes as follows: the compiler sets the __qualname__ at the
beginning of the class body. W
This PEP is now accepted for inclusion in Python 3.6. Martin,
congratulations! Someone (not me) needs to review and commit your
changes, before September 12, when the 3.6 feature freeze goes into
effect (see https://www.python.org/dev/peps/pep-0494/#schedule).
On Sun, Jul 17, 2016 at 4:32 AM, Mart
Hi Guido, Hi Nick, Hi list,
so I just updated PEP 487, you can find it here:
https://github.com/python/peps/pull/57 if it hasn't already been
merged. There are no substantial updates there, I only updated the
wording as suggested, and added some words about backwards
compatibility as hinted by Nic
