Bug 712122 - mod_wsgi warning on different python versions
Summary: mod_wsgi warning on different python versions
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mod_wsgi
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Joe Orton
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-09 14:38 UTC by Scott Dodson
Modified: 2012-01-27 15:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-27 15:23:28 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Scott Dodson 2011-06-09 14:38:38 UTC 
Description of problem:
[Thu Jun 09 10:13:18 2011] [warn] mod_wsgi: Compiled for Python/2.6.2.
[Thu Jun 09 10:13:18 2011] [warn] mod_wsgi: Runtime using Python/2.6.5.


Version-Release number of selected component (if applicable):
python-2.6.5-3.el6_0.2.x86_64
mod_wsgi-3.2-1.el6.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Install mod_wsgi in RHEL 6.0

  
Actual results:
Warning messages in apache error log.

Expected results:
No warning messages.

Additional info:
Comment 2 Joe Orton 2011-06-24 11:46:45 UTC 
Thanks for the report.  This message is harmless, in case that was a concern.
Comment 3 RHEL Program Management 2011-07-06 01:37:08 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Note You need to log in before you can comment on or make changes to this bug.