Bug 1230802
| Summary: | Backport of upstream bug #7316 for python 2.7 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Flavio Grossi <flaviogrossi> | ||||||
| Component: | python | Assignee: | Charalampos Stratakis <cstratak> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 24 | CC: | bkabrda, dmalcolm, ivazqueznet, jberan, jonathansteffan, ncoghlan, pviktori, tomspur, tradej | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-08-08 11:59:00 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Flavio Grossi
2015-06-11 14:40:07 UTC
Created attachment 1037734 [details]
test program to expose the bug
Even if this change doesn't get accepted upstream, I think it would be a good improvement to the previously applied downstream extension to the API, as it makes it consistent with Python 3 for the benefit of single source Python 2/3 code. For those interested, the new upstream bug is http://bugs.python.org/issue25084 and to me the only blocker, as noted there, is the need to backport the patch to other thread implementations. Which ones are of interest for RedHat/Fedora? The only one seems to be thread_pth.h but it seems to me not to be used right now. As far as I am aware, thread_pthread is the only threading backend used in Fedora and RHEL, so I'd be fine with a patch that threw RuntimeError if the timeout argument was set to a non-default value and a backend other than pthreads was in use. Bringing over some of my Fedora (et al) specific comments from the upstream issue, the current situation we have in regards to the system Python is: * Python 2 only code can pass "balanced=False" (but probably wouldn't want to due to the potential increase in wake-up latency) * Python 3 only code can specify a timeout directly * Single source Python 2/3 code that supports both Fedora and RHEL/CentOS 7 can't do either (since the API signatures are different) If we update the Python 2.7 patch to be a backport of the Python 3 threading timeout API and implementation, then not only is the system Python better behaved by default, but the explicit timeout API becomes usable in single source Python 2/3 code (once the API fix is makes its way into a RHEL/CentOS 7 point release) any news on this issue? This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |