#3279: python-mysql-1.2.0 has a bug with threading, raising 'ReferenceError:
weakly-referenced object no longer exists'
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: closed | Component: Documentation
Version: SVN | Resolution: worksforme
Keywords: | Stage: Design decision
needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------+---------------------------------------
Changes (by [EMAIL PROTECTED]):
* summary: threading fastcgi does not work with mysql, raising
'ReferenceError: weakly-referenced object no
longer exists' => python-mysql-1.2.0 has a bug
with threading, raising 'ReferenceError:
weakly-referenced object no longer exists'
* component: Core framework => Documentation
* stage: Accepted => Design decision needed
Comment:
Aha! Found this in the mailing list archives:
http://wolfram.kriesing.de/blog/index.php/2006/multithreading-with-
mysqldb-and-weakrefs
python-mysql-1.2.0 has a problem with multithreading. Please upgrade.
1.2.1p2 has been reported to solve this. Thanks, Wolfram Kriesing!
Are you two able to test this?
@core: Should we add a warning to the docs?
--
Ticket URL: <http://code.djangoproject.com/ticket/3279#comment:9>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
