Skip to content

Tracking issue: remaining stdlib heavy-function bytecode parity gaps #29

@youknowone

Description

@youknowone

Summary

This is a tracking issue for the remaining large bytecode parity gaps in tracked stdlib/test files after the
LOAD_SMALL_INT direct parity work. Most of these are expected to collapse as the root-cause issues for CFG
normalization, slice folding, borrow opcode selection, and PEP 695/annotation code generation are fixed.

Current high-diff tracked files

  • Lib/test/test_buffer.py
  • Lib/test/test_dis.py
  • Lib/test/test_math.py
  • Lib/test/test_tarfile.py
  • Lib/test/test_typing.py
  • Lib/test/test_annotationlib.py
  • Lib/test/test_type_aliases.py
  • Lib/dataclasses.py
  • Lib/test/test_codecs.py
  • Lib/test/test_inspect/test_inspect.py

Representative hot spots

  • test_buffer.py::TestBufferProtocol.*
  • test_math.py::MathTests.testFsum
  • test_math.py::MathTests.testSumProd
  • test_math.py::MathTests.test_sumprod_stress
  • dataclasses.py::_process_class
  • test_tarfile.py extraction / write / context-manager helpers

Policy

Do not paper over these diffs with file-specific hacks in Lib/. Fix them through shared compiler structure
so that multiple files collapse at once.

Done when

The file list above drops out of the top compare_bytecode.py report as the root-cause issues are fixed, and
tracked stdlib/test files converge toward CPython without special-case patches.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions