Fix tuple subclass preservation in type bases - #8420
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
📦 Library DependenciesThe following Lib/ modules were modified. Here are their dependencies: [ ] lib: cpython/Lib/csv.py dependencies:
dependent tests: (4 tests)
[ ] test: cpython/Lib/test/test_dict.py (TODO: 6) dependencies: dependent tests: (no tests depend on dict) [x] lib: cpython/Lib/types.py dependencies:
dependent tests: (57 tests)
[x] lib: cpython/Lib/ast.py dependencies:
dependent tests: (149 tests)
Legend:
|
Store validated base classes in the original typed tuple, while retaining a bootstrap vector only until a Python tuple can be materialized. Assisted-by: gpt-5.6-sol
Initialize tuple and the canonical empty tuple alongside type and object so every type stores an actual typed bases tuple from construction. Remove the bootstrap bases representation and keep raw initialization Miri-safe. Assisted-by: Codex:gpt-5.6-sol
Summary