Bug 2280968
| Summary: | python-ipdb fails to build with Python 3.13: ImportError: No module named my_buggy_module_3_11 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Karolina Surma <ksurma> |
| Component: | python-ipdb | Assignee: | Troy Curtis <troy> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | fti-bugs, jeremy, troy |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-09-05 01:17:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2260875, 2260877, 2300529, 2244836, 2291914 | ||
It looks like there was some restructuring in the CPython pdb module which ipdb leverages. I've created an issue upstream [0] though I'm not too hopefully there will be much immediate activity on it. I'll also try to get to the bottom of the issue, but I'm not that familiar with the specifics of the implementation of either ipdb or CPython's pdb module. (In reply to Troy Curtis from comment #1) > It looks like there was some restructuring in the CPython pdb module which > ipdb leverages. I've created an issue upstream [0] though I'm not too > hopefully there will be much immediate activity on it. I'll also try to get > to the bottom of the issue, but I'm not that familiar with the specifics of > the implementation of either ipdb or CPython's pdb module. I forgot to include the link to the upstream issue: https://github.com/gotcha/ipdb/issues/279 *** Bug 2291742 has been marked as a duplicate of this bug. *** This package has failed to build with Python 3.13 so far. Fedora 41 is already in the Beta Freeze phase. What's your plan going forward? Will the package be fixed in time for the Final Freeze of Fedora 41 (planned on Oct 15th 2024)? If you don't plan or can't fix the package before Fedora 41 goes into the Final Freeze phase, please retire the package. You can unretire it anytime during the Fedora 41 lifecycle - doing this now will simply ensure that we don't release Fedora with a broken package. Thank you! Yes this is a good point. I've looked at it a little bit, but it is certainly hooking into areas I'm not familiar with in Python, so I probably won't have a chance to fix it soon. So far there is no activity on my reported issue either. I've looked around to see if there are any other patches around, but Fedora is leading the Python charge as usual so there is no one else work I can copy from ;). I'll retire it, as you say, it isn't truly permanent. Retired in branched and rawhide. |
python-ipdb fails to build with Python 3.13.0b1. test_debug_module_script_3_11 (tests.test_opts.OptsTest.test_debug_module_script_3_11) ... ImportError: No mo ..dule named my_buggy_module_3_11 4 The program exited via sys.exit(). Exit status: 1 https://docs.python.org/3.13/whatsnew/3.13.html For all our attempts to build python-ipdb with Python 3.13, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/python-ipdb/ Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.13: https://copr.fedorainfracloud.org/coprs/g/python/python3.13/ Let us know here if you have any questions. Python 3.13 is planned to be included in Fedora 41. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.13. A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon. We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.