https://bugzilla.suse.com/show_bug.cgi?id=1213698 Bug ID: 1213698 Summary: We have .cpython-311.pyc in non-311 packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers@suse.com Reporter: mcepl@suse.com QA Contact: qa-bugs@suse.de CC: bwiedemann@suse.com Target Milestone: --- Found By: --- Blocker: --- I have been reminded about this: -/usr/lib/python3.9/site-packages/blinker/__pycache__/base.cpython-311.pyc 6e33550a94efe8668e6b60422f1a674c9844fd6c44e92c0afcc5d98e71cf51cb 0 +/usr/lib/python3.9/site-packages/blinker/__pycache__/base.cpython-311.pyc 0b7e8cb203ad88028706b7204f007bb66a860cf3cfd6ebde4964a4caf6c248ef 0 why are 311.pyc files in the 3.9 path? We run make html without specifying Python used. It runs the Sphinx builder with /usr/bin/python3 which is now Python 3.11 and it loads (and generates *.pyc) when collecting information on the installed libraries. Suggested solution is https://stackoverflow.com/q/34025113/164233 and I have tried it in https://build.opensuse.org/request/show/1100942 However, it seems like too complicated problem (patching every package). Any other ideas? -- You are receiving this mail because: You are on the CC list for the bug.