--
Ticket URL: <https://code.djangoproject.com/ticket/18377>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
Do you know which version of pylibmc fixed the problem?
If this issue is well documented, we could add a check on the version of
pylibmc and refuse to start with a buggy version.
--
Ticket URL: <https://code.djangoproject.com/ticket/18377#comment:1>
Comment (by aaugustin):
I suppose it's https://github.com/lericson/pylibmc/issues/34, which is a
duplicate of https://github.com/lericson/pylibmc/pull/19.
This is the "Fixed GIL issues" item of version 1.2.0. So the requirement
would be pylibmc >= 1.2.
I don't know exactly how often the problem happens. Is it systematic under
mod_wsgi?
--
Ticket URL: <https://code.djangoproject.com/ticket/18377#comment:2>
* status: new => closed
* resolution: => needsinfo
Comment:
Closing as needsinfo since we haven't gotten further clarification about
the issue and newer versions of Debian are now available which presumably
have a more recent version of pylibmc. If someone would like to provide a
patch, please reopen.
--
Ticket URL: <https://code.djangoproject.com/ticket/18377#comment:3>