Comments on: Beware of using Pylibmc 1.1+ and mod_wsgi http://www.dctrwatson.com/2010/09/beware-of-using-pylibmc-1-1-and-mod_wsgi/ The odyssey of a philomath of technology Wed, 20 May 2015 19:59:28 +0000 hourly 1 http://wordpress.org/?v=4.1.6 By: Igor http://www.dctrwatson.com/2010/09/beware-of-using-pylibmc-1-1-and-mod_wsgi/#comment-9720 Wed, 20 Jul 2011 08:02:00 +0000 http://www.dctrwatson.com/?p=46#comment-9720 Thanks a lot !!!! Great help!

]]>
By: Day Barr http://www.dctrwatson.com/2010/09/beware-of-using-pylibmc-1-1-and-mod_wsgi/#comment-9714 Fri, 25 Mar 2011 17:04:00 +0000 http://www.dctrwatson.com/?p=46#comment-9714 For others googling their way here after stumbling into this issue, it has been fixed, but not in a version released to pypi. It would be nice to be able to

pip install pylibmc==1.2

but until a new 1.2 release is made, doing

pip install pylibmc -e git+https://github.com/lericson/pylibmc.git@47cb9ef9ff5c3cf25c9c#egg=Package

will give you a version built from the source in git (latest as of right now). For reference, the github issue is https://github.com/lericson/pylibmc/issues/19

]]>
By: Doctor Watson http://www.dctrwatson.com/2010/09/beware-of-using-pylibmc-1-1-and-mod_wsgi/#comment-31 Fri, 10 Sep 2010 21:21:00 +0000 http://www.dctrwatson.com/?p=46#comment-31 I assume using with gunicorn it’s a little easier than having to do this bit of fun with Apache/mod_wsgi: http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Python_Interactive_Debugger

]]>
By: Doctor Watson http://www.dctrwatson.com/2010/09/beware-of-using-pylibmc-1-1-and-mod_wsgi/#comment-30 Fri, 10 Sep 2010 21:14:00 +0000 http://www.dctrwatson.com/?p=46#comment-30 Hi,

Using Py_{BEGIN,END}_ALLOW_THREADS would fix the issue. The “get” method implements those macros and there are no issues. The thread doesn’t kludge until a “set” is called.

I agree the GIL practices are a little convoluted for Python C developers. I honestly did not know about the GIL until I started debugging this issue. (I have not done Python C writing though)

]]>
By: Ludvig Ericson http://www.dctrwatson.com/2010/09/beware-of-using-pylibmc-1-1-and-mod_wsgi/#comment-29 Fri, 10 Sep 2010 20:47:00 +0000 http://www.dctrwatson.com/?p=46#comment-29 I’m not sure the previous comment’s name was updated to my name, but I’m Ludvig Ericson, the main developer of pylibmc.

]]>
By: Ludvig Ericson http://www.dctrwatson.com/2010/09/beware-of-using-pylibmc-1-1-and-mod_wsgi/#comment-28 Fri, 10 Sep 2010 20:46:00 +0000 http://www.dctrwatson.com/?p=46#comment-28 Hi. I was unaware of this; in fact I didn’t really implement GIL handling myself, so I apologize for this behavior from pylibmc– however, I think it GIL practices could be more clear for Python C API developers, seeing as this isn’t exactly my first C extension and yeah…

Would using Py_{BEGIN,END}_ALLOW_THREADS fix this issue? From my reading the manual, it seems this would be compatible with multiple interpreters within one process.

]]>
By: Tweets that mention Beware of using Pylibmc 1.1+ and mod_wsgi « Dctr Watson -- Topsy.com http://www.dctrwatson.com/2010/09/beware-of-using-pylibmc-1-1-and-mod_wsgi/#comment-27 Fri, 10 Sep 2010 02:33:13 +0000 http://www.dctrwatson.com/?p=46#comment-27 […] This post was mentioned on Twitter by John Watson and Aaron, John Watson. John Watson said: New post: Beware of using Pylibmc 1.1+ and mod_wsgi http://j.mp/bGHXHO […]

]]>