[Bug 759943] Re: mod_wsgi.so-3.2 gives errors
Barry Warsaw
759943 at bugs.launchpad.net
Fri Apr 15 15:56:39 UTC 2011
<barry> jamespage: http://docs.python.org/dev/whatsnew/3.2.html [11:48]
<barry> "The misleading functions PyEval_AcquireLock() and
PyEval_ReleaseLock() have been officially deprecated. The thread-state
aware APIs (such as PyEval_SaveThread() and PyEval_RestoreThread())
should be used instead."
<barry> i see PyEval_AcquireLock in the error logs so perhaps mod_wsgi is
using those api's incorrectly [11:49]
<jamespage> barry: upstream trunk has removed all but one call to
PyEval_AcquireLock() so I guess its something todo with that.
<barry> jamespage: yep, highly likely
<barry> jamespage: i guess mod_wsgi totally unusable in natty w/py3.2?
<jamespage> barry: yep - even "Hello World" would not work
<jamespage> barry: my feel would be to remove the python3.2 built version of
the module for natty; and sync up again next release when upstream
officially support. [11:51]
<barry> jamespage: seems reasonable. i wonder if doko or ScottK can chime in
<barry> jamespage: and we can always build the new version in a ppa for natty
<ScottK> barry: I think POX and bzed would be the ones to hear from. [11:53]
<ScottK> (since they are the mod-wsgi maintainers)
The upshot is that mod-wsgi won't work for Python 3.2 in natty. Is it
worth removing the 3.2 build for natty?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/759943
Title:
mod_wsgi.so-3.2 gives errors
More information about the Ubuntu-server-bugs
mailing list