You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was just a pull request merged into Python 3.12 to change how types.get_original_bases() behaves for generic types whose bases have no type arguments.
The TL;DR is that types.get_original_bases(cls) should only use cls's own__orig_bases__, not an ancestor type's via MRO, and should fall back to cls.__bases__ otherwise.
The text was updated successfully, but these errors were encountered:
There was just a pull request merged into Python 3.12 to change how
types.get_original_bases()
behaves for generic types whose bases have no type arguments.__orig_bases__
are our own inget_original_bases
cpython#107584The TL;DR is that
types.get_original_bases(cls)
should only usecls
's own__orig_bases__
, not an ancestor type's via MRO, and should fall back tocls.__bases__
otherwise.The text was updated successfully, but these errors were encountered: