364583 – www-apache/mod_wsgi-3.3 doesn't work with Python 3.2

Bug 364583 - www-apache/mod_wsgi-3.3 doesn't work with Python 3.2

Summary: www-apache/mod_wsgi-3.3 doesn't work with Python 3.2

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Dirkjan Ochtman (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	python-3.2
	Show dependency tree

Reported:	2011-04-23 16:23 UTC by Chris Mayo
Modified:	2011-05-15 19:12 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

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

Note You need to log in before you can comment on or make changes to this bug.

Description Chris Mayo 2011-04-23 16:23:34 UTC

Although mod_wsgi compiles with mod_wsgi-3.3-python-3.2.patch of Fri Apr 22 when running it I repeatedly get:

Fatal Python error: PyEval_AcquireLock: current thread state is NULL
Fatal Python error: PyEval_AcquireLock: current thread state is NULL
[] [notice] child pid 4670 exit signal Aborted (6)
[] [info] mod_wsgi (pid=4670): Process 'aaaa' has died, restarting.

I think it needs the patch from
http://code.google.com/p/modwsgi/source/detail?r=d40a1bf6b9ad9cacc50caf0b3806b9a231e0d4d7

as well.

(Using WSGIDaemonProcess)

Comment 1 Arfrever Frehtes Taifersar Arahesis (RETIRED) gentoo-dev

2011-05-11 19:13:38 UTC

I have backported this patch. Please test if www-apache/mod_wsgi-3.3 now works for you with Python 3.2.

Comment 2 Chris Mayo 2011-05-15 19:12:05 UTC

Seems good to me. Thanks.