Closed GoogleCodeExporter closed 9 years ago
Can you try 1.0b2? The 0.13.6 has a known issues with monkey patching
threading.
You can get it from http://code.google.com/p/gevent/downloads/list
Original comment by Denis.Bi...@gmail.com
on 11 Apr 2012 at 7:49
sure - I don't perceive this as a gevent bug - if something imports something
before you can run monkey patch, there's not much you can do right?
I just wanted to put it up so that at least if someone else runs into it, they
can see this. I'll run a test and let you know whatI find.
Original comment by h...@continuum.io
on 11 Apr 2012 at 7:51
Ideally monkey patching should work even after the import (if possible). So if
we can fix it we should.
Original comment by Denis.Bi...@gmail.com
on 11 Apr 2012 at 7:53
I'm not 100% sure this is the same, but this sounds very close to an issue I
had with pycassa and gevent. The answer in that case was a secondary
monkey-patching of the stdlib Queue to use the Queue from gevent as shown here:
https://github.com/phus/geventmonkey/blob/master/geventcassa.py
The geventmonkey lib has several other sets of monkey patches to help other 3rd
party libraries work properly. Do those belong in gevent itself? Seems kind of
a pain to have these separate, at the very least they should be in a blessed
gevent-patch repo or something so that everyone ideally uses the same monkey
patch.
Original comment by b...@groovie.org
on 16 Apr 2012 at 8:11
[deleted comment]
[deleted comment]
Migrated to http://github.com/SiteSupport/gevent/issues/122
Original comment by Denis.Bi...@gmail.com
on 14 Sep 2012 at 10:52
Original issue reported on code.google.com by
h...@continuum.io
on 11 Apr 2012 at 6:23