[issue34422] __name__ not available for classes in typing module

2021-08-02 Thread Ken Jin
Ken Jin added the comment: Agree with Yurii. This is no longer an issue in 3.10 onwards. Thanks to Yurii for providing the fix in the other issue. -- nosy: +kj resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue34422] __name__ not available for classes in typing module

2021-08-02 Thread Yurii Karabas
Yurii Karabas <1998uri...@gmail.com> added the comment: I believe we can close this issue. It has been fixed in scope of this issue - https://bugs.python.org/issue44524 -- nosy: +uriyyo ___ Python tracker

[issue34422] __name__ not available for classes in typing module

2020-09-17 Thread Irit Katriel
Change by Irit Katriel : -- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python versions: +Python 3.10, Python 3.9 -Python 3.7, Python 3.8 ___ Python tracker

[issue34422] __name__ not available for classes in typing module

2018-08-19 Thread Ivan Levkivskyi
Change by Ivan Levkivskyi : -- Removed message: https://bugs.python.org/msg323770 ___ Python tracker ___ ___ Python-bugs-list

[issue34422] __name__ not available for classes in typing module

2018-08-19 Thread Ivan Levkivskyi
Ivan Levkivskyi added the comment: This is an intentional change. It would be a bad idea to use `__name__` instead of what is currently `_name`, because semantics is subtly different. Also the fact that types in typing module used to be actual class objects was an implementation detail

[issue34422] __name__ not available for classes in typing module

2018-08-19 Thread Ivan Levkivskyi
Ivan Levkivskyi added the comment: Oh I just re-read my comment and there are so many typos that I will write a new one, sorry. -- ___ Python tracker ___

[issue34422] __name__ not available for classes in typing module

2018-08-19 Thread Ivan Levkivskyi
Ivan Levkivskyi added the comment: This is an intentional change. It would be a bad idea to use `_name` instead of `__name__`, because semantics is subtly different. Also the fact that type in typing object used to be actual class object was an implementation detail (also typing is still

[issue34422] __name__ not available for classes in typing module

2018-08-19 Thread Serhiy Storchaka
Change by Serhiy Storchaka : -- components: +Library (Lib) -Interpreter Core nosy: +gvanrossum, levkivskyi versions: +Python 3.8 ___ Python tracker ___

[issue34422] __name__ not available for classes in typing module

2018-08-19 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: Bisecting this issue revealed that this happened on commit d911e40e788fb679723d78b6ea11cabf46caed5a is the first bad commit commit d911e40e788fb679723d78b6ea11cabf46caed5a Author: Ivan Levkivskyi Date: Sat Jan 20 11:23:59 2018 + bpo-32226:

[issue34422] __name__ not available for classes in typing module

2018-08-17 Thread Gabriel Tremblay
New submission from Gabriel Tremblay : Types under the typing module used to behave like other python classes regarding the __name__ attribute before Python 3.7. The behavior seems to have changed to a non-standard way. Py3.6 >>> from typing import List >>> dir(List) ['__abstractmethods__',