[issue11339] annotation for class being defined

Change by Irit Katriel : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue11339] annotation for class being defined

Jelle Zijlstra added the comment: Agree. typing.Self from PEP 673 fixes this specific case, and PEP 563 or 649 will provide a general solution. No need to keep this issue open. -- nosy: +JelleZijlstra status: pending -> open ___ Python tracker

[issue11339] annotation for class being defined

Irit Katriel added the comment: This looks like PEP 673 – Self Type. -- nosy: +iritkatriel resolution: -> out of date status: open -> pending ___ Python tracker ___

[issue11339] annotation for class being defined

Change by Kamil Turek : -- nosy: +kamilturek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue11339] annotation for class being defined

Karthikeyan Singaravelan added the comment: Is this issue resolved with PEP 563 and the behavior becoming default in Python 3.10? https://www.python.org/dev/peps/pep-0563/#forward-references -- nosy: +xtreak ___ Python tracker

[issue11339] annotation for class being defined

Change by Socob <206a8...@opayq.com>: -- nosy: +Socob ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue11339] annotation for class being defined

Changes by Ivan Levkivskyi : -- nosy: +levkivskyi ___ Python tracker ___ ___

[issue11339] annotation for class being defined

Changes by Ryan Hiebert : -- nosy: +ryanhiebert ___ Python tracker ___ ___

[issue11339] annotation for class being defined

Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11339 ___ ___ Python-bugs-list

[issue11339] annotation for class being defined

Changes by Eric Snow ericsnowcurren...@gmail.com: -- nosy: +ericsnow ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11339 ___ ___ Python-bugs-list

[issue11339] annotation for class being defined

Terry J. Reedy tjre...@udel.edu added the comment: The basic problem is that the class object is defined after the class definitions have been made, I have sometimes thought the the class statement could start with binding the name to a blank object or new, blank class object. But then people

[issue11339] annotation for class being defined

Raymond Hettinger rhettin...@users.sourceforge.net added the comment: This would be an important fix-up if we could find some way to implement it. The basic problem is that the class object is defined after the class definitions have been made, so the target of the Graph reference isn't known

[issue11339] annotation for class being defined

Changes by Raymond Hettinger rhettin...@users.sourceforge.net: -- Removed message: http://bugs.python.org/msg129656 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11339 ___

[issue11339] annotation for class being defined

Raymond Hettinger rhettin...@users.sourceforge.net added the comment: This would be an important fix-up if we could find some way to implement it. The basic problem is that the class object is defined after the class definitions have been made, so the target of the Graph reference isn't known

[issue11339] annotation for class being defined

Changes by Raymond Hettinger rhettin...@users.sourceforge.net: -- Removed message: http://bugs.python.org/msg129657 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11339 ___

[issue11339] annotation for class being defined

Raymond Hettinger rhettin...@users.sourceforge.net added the comment: class Prepared(type): 'Preload the class with a reference to itself' @classmethod def __prepare__(mcl, name, bases): return {name: type(name, bases, {})} def __new__(mcl, name, bases, mapping):

[issue11339] annotation for class being defined

Changes by Raymond Hettinger rhettin...@users.sourceforge.net: -- Removed message: http://bugs.python.org/msg129659 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11339 ___

[issue11339] annotation for class being defined

Raymond Hettinger rhettin...@users.sourceforge.net added the comment: This would be an important fix-up if we could find some way to implement it. The basic problem is that the class object is defined after the class definitions have been made, so the target of the Graph reference isn't known

[issue11339] annotation for class being defined

Changes by Armin Rigo ar...@users.sourceforge.net: -- nosy: -arigo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11339 ___ ___ Python-bugs-list

[issue11339] annotation for class being defined

Changes by Daniel Urban urban.dani...@gmail.com: -- nosy: +durban ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11339 ___ ___ Python-bugs-list

[issue11339] annotation for class being defined

Raymond Hettinger rhettin...@users.sourceforge.net added the comment: Until and unless this gets fixed, perhaps we should document some sort of workaround. One possibility is attached. -- Added file: http://bugs.python.org/file20941/annotations_workaround.py

[issue11339] annotation for class being defined

New submission from Andy Harrington ahar...@luc.edu: You cannot make a self-referential annotation like class Graph: def reverse(self) - Graph: # ... This corresponds to a common coding situation. -- components: Interpreter Core messages: 129587 nosy: andyharrington

[issue11339] annotation for class being defined

Benjamin Peterson benja...@python.org added the comment: This has been true forever. I suggest you try python-ideas. -- nosy: +benjamin.peterson resolution: - rejected status: open - closed ___ Python tracker rep...@bugs.python.org