Re: Odd types.get_original_bases() behavior for classes with generic bases but no type arguments

> >>> Example.__bases__ > (First, Second) Sorry, that should have been >>> Example.__bases__ (, ) That's what I get for writing an example from memory rather than copying it from a REPL session. It doesn't change the point I wanted to make, though. Thanks, Chris Bouchard -- https://mail.python

Odd types.get_original_bases() behavior for classes with generic bases but no type arguments

(Apologies if this has already been discussed. I tried to search and didn't find anything relevant.) I was playing around with 3.12.0b4 this evening and noticed an odd (to me, at least) behavior with types.get_original_bases(). I hesitate to call it a bug because I think I understand *why* it's be