Hi Larry,
I'm afraid I don't have any experience using gevent with wsgi, perhaps you
could try posting directly on the Google group
https://groups.google.com/forum/#!forum/gevent
On Mon, 16 May 2016, 20:28 Larry Martell, wrote:
> I don't see it either. I posted it twice - M
Does anyone here use gevent? I posted a question on the gevent mailing
list, here, and on SO and did not get any replies on any of them. I
have a client that is using it - I had never heard of it before, and
now I am wondering how big the user base and community is.
--
https://mail.python.org
I have a python server that has this in the main:
from gevent import pywsgi
try:
httpd = pywsgi.WSGIServer(('0.0.0.0', 8000), app)
httpd.serve_forever()
except KeyboardInterrupt:
pass
Recently we began getting HTTPError: 504 Server Error: Gateway
Time-out on requests to
Some people have tried to make a case that concurrent.futures should be adopted
as a replacement wherever greenlet based algorithms are in use. However, my
experience is that greenelts combined with concurrent.futures provides
significant advantages. In other words, to a degree the two approache
On 2013-10-18, James Harris wrote:
> "Roy Smith" wrote in message
> news:l3riea$82$1...@panix2.panix.com...
>> I'm running:
>>
>> Ubuntu Precise
>> Python 2.7.3
>> django 1.4.5
>> gunicorn 0.17.4
>> gevent 1.0dev (rc3)
>>
&g
I forgot to mention that the connect()/send() code works just fine if I switch
my gunicorn config from gevent to sync workers.
--
https://mail.python.org/mailman/listinfo/python-list
"Roy Smith" wrote in message
news:l3riea$82$1...@panix2.panix.com...
> I'm running:
>
> Ubuntu Precise
> Python 2.7.3
> django 1.4.5
> gunicorn 0.17.4
> gevent 1.0dev (rc3)
>
> I haven't been able to pin this down exactly, but it looks like if I
&g
I'm running:
Ubuntu Precise
Python 2.7.3
django 1.4.5
gunicorn 0.17.4
gevent 1.0dev (rc3)
I haven't been able to pin this down exactly, but it looks like if I
do (inside of a custom logging.Handler subclass):
# Paraphrased from the actual code
remote_addr = ("l
Hi,
One problem, thanks for help.
import gevent.monkey
gevent.monkey.match_all()
from lxml import etree
# I using xpath parse the html
def _get(p):
url = BUILD_URL(p)
html = urllib2.urlopen(url)
# RUN AT HERE AND BLOCKING
# ver1
tree = etree.parse(html, parse)
# ver
GOAL:spawn a few greenlet worker deal with the data pop from redis (pop from
redis and then put into queue)
RUNNING ENV: ubuntu 12.04
PYTHON VER: 2.7
GEVENT VER: 1.0 RC2
REDIS VER:2.6.5
REDIS-PY VER:2.7.1
from gevent import monkey; monkey.patch_all()
import gevent
from gevent.pool import Group
ation.
Could concurrent.futures be a (partly) replacement of gevent?
I guess not, because gevent provide lightweight thread via greenlet,
while concurrent.futures only provide multiprocessing across different
processor) (not lightweight).
Thanks
--
http://mail.python.org/mailman/listinfo/python-list
On 07.07.2012 09:09, self.python wrote:
(I'm very new to this coroutine part
so It's not supposed to attack these modules,
just I don't know the differences)
atfer version 2.5, python officially support coroutine with yield.
and then, why greenlet, gevent, Stackless python are st
r
2012년 7월 7일 토요일 오후 4시 33분 26초 UTC+9, Devin Jeanpierre 님의 말:
> On Sat, Jul 7, 2012 at 3:09 AM, self.python wrote:
> > it there somthing that "yield" can't do
> > or just it is easier or powerful?
>
> couroutine-like generators can't give up control flow unless they are
> the top level function
On Sat, Jul 7, 2012 at 3:09 AM, self.python wrote:
> it there somthing that "yield" can't do
> or just it is easier or powerful?
couroutine-like generators can't give up control flow unless they are
the top level function handled by the coroutine controller thing. For
example, we can do this:
(I'm very new to this coroutine part
so It's not supposed to attack these modules,
just I don't know the differences)
atfer version 2.5, python officially support coroutine with yield.
and then, why greenlet, gevent, Stackless python are still useful?
it there somthing that &quo
15 matches
Mail list logo
