Red Hat Bugzilla – Bug 506367
CherryPy version 3.1.2 is required to work with Python 2.6
Last modified: 2016-09-19 22:39:55 EDT
Description of problem:
_cpchecker.py replaces warnings.formatwarning, and the argument
list was not consistent with the definition in Python 2.6 until
CherryPy version 3.1.2. Fedora 11 is currently shipping version
3.1.1, without the necessary patch.
Version-Release number of selected component (if applicable):
N/A - the code in this package simply doesn't contain the needed
CherryPy ticket discussing this issue:
CherryPy patch in version 3.1.2 resolving this issue:
Python ticket discussing this issue:
Does this break cherrypy to the point that 3.1.1 is unusable on python-2.6? I'm pushing an update but need to decide whether to push to testing or directly to stable.
If the CherryPy checker is enabled, which it is by default, then
any warning it produces will become a fatal exception that prevents
the application from starting up. If your code produces no warnings,
then it will still be able to run.
To test this, you can begin with the scaffold sample application
and add these two lines to the end of example.conf:
(This would ordinarily produce a warning, but with CherryPy 3.1.1
and Python 2.6, the application cannot start.)
Since the fatal error only occurs when you would have otherwise
received a warning, it may not be critical enough to bypass testing;
we'll rely on your judgment. Thanks for the quick reply!
python-cherrypy-3.1.2-1.fc11 has been submitted as an update for Fedora 11.
python-cherrypy-3.1.2-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update python-cherrypy'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-6702
python-cherrypy-3.1.2-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.