5

I think it’d also be okay to change in the beta period - some build backends may need to do work and a new release, but that pain is limited and may be worth it, under one condition: this really needs a proper integration test in CPython, not just for extension names but for interleaved multi-architecture builds, with the test checking that if two builds have files with the same name, their content is identical (one job building for Linux x86-64 and aarch64 should be enough). Because this is the second release in a row where this issue has surfaced too late. For 3.14 it was build-details.json, now it’s filename extensions. For whatever packaging feature is next, this should be caught before merging the feature, not after support for it has been shipped in build systems and backends.

6 Likes