[issue44057] Inconsitencies in `__init_subclass__` in a generic class

Ken Jin added the comment: Since this only affects 3.6 which is no longer receiving bugfixes, I'm closing this issue. 3.7 and higher do not have this bug. So one way forward is to upgrade to 3.7 or 3.8 - both of which are supported by most major libraries. If this bug reappears again in 3.1

[issue44057] Inconsitencies in `__init_subclass__` in a generic class

Erez Zinman added the comment: Also Tensorflow. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue44057] Inconsitencies in `__init_subclass__` in a generic class

Erez Zinman added the comment: You're right. I accidentally used 3.6.9 both times. Thank you anyway. Regardless, that's unfortunate that you don't support the version 3.8 anymore, since many frameworks do not officially support 3.9 as of yet (pytorch, for example). --

[issue44057] Inconsitencies in `__init_subclass__` in a generic class

Ken Jin added the comment: Hi Erez, thank you for the bug report. What minor version of 3.8 are you using exactly? I'm able to reproduce this on 3.6.8, but not on 3.8.5. BTW, Python 3.8 is no longer receiving bugfixes - only security fixes. The only versions still getting bugfixes right now

[issue44057] Inconsitencies in `__init_subclass__` in a generic class

Change by Karthikeyan Singaravelan : -- nosy: +gvanrossum, levkivskyi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue44057] Inconsitencies in `__init_subclass__` in a generic class

New submission from Erez Zinman : The following behavior was witnessed in v3.6 & v3.8. When deriving from a Generic base class, there's an inconsistency in the order of operation within the `__new__()` function between the case of deriving WITH generic-argument specification and WITHOUT. It