SuPPort: Evented Python servers

https://www.paypal-engineering.com/2015/03/17/introducing-support/

by mhashemi • 11 years ago

51 12 11 years ago

kenrikm• 11 years ago

Interesting this is built using gevent since in Python 3.4 things are moving away from gevent in favor of Asyncio. The last time I checked (a few months ago) gevent is only supported on Py2.7 unless you're using a fork that has patched Py3 support which still has a number of outstanding bugs. I'm curious what the migration path is going to look like to 3.0+ since 2.7 is near EOL (2020?).

mhashemi4• 11 years ago

That's a pretty coarse description of the Python concurrency landscape. "things are moving away"?

For one, there was never really official Python backing for gevent and other coroutine-oriented programming models. Remember asyncore? From our standpoint, Python 2.7 continues to be the industry standard, and we'll continue to target it for the foreseeable future. Should some major internal or open-source use case come along and make it advantageous for us to target Python 3, we would approach it like any other feature request. Python 2 will not be vanishing from beneath your feet anytime soon. ;)

scrollaway2• 11 years ago

It's less about where Python 2.7 is going and more about where the libraries themselves are going. If you use a library which is considered deprecated by a large part of the python community, don't be surprised not to aspire new contributors.

No one expects 2.7 to go away, that doesn't mean contributors want to deal with Python 2 when 3 is available elsewhere.

kapilvt• 11 years ago

stack looks solid, coroutine, stats, and utilities, i'm interested in giving it a spin. some interesting libraries in there i haven't seen before. even then its hard to reconcile statements like native gevent (sans monkey) with libraries like flask (thread locals) or even the std lib. one of the main benefits of gevent vs twisted or other async libs is the ability to actual reuse the python ecosystem via a handful of monkey patched modules, a position which this stack effectively disavows.

mhashemi4• 11 years ago

gevent has lots of benefits outside monkeypatching! That said, historically we mostly chose gevent as it seemed like the better interface to greenlet, which we really liked. For the most part, we were (and in many cases still are) trying to cater to a Python community of beginners. Greenlet-based approaches seemed easier to explain than other options, and sure enough we rarely hear complaints about development complexity, etc.

morekozhambu• 11 years ago

OK kind of TLDR; I just took the packages that they use from the link they had provided.

boltons==0.4.1

cffi==0.8.6

clastic==0.4.2

cryptography==0.7.2

enum34==1.0.4

faststat==0.3.1

gevent==1.0.1

greenlet==0.4.5

hyperloglog==0.0.9

lithoxyl>=0.1.0

psutil==2.2.1

py==1.4.26

pyasn1==0.1.7

pycparser==2.10

pyjks>=0.3.0.1

pyOpenSSL==0.14

pytest==2.6.4

sampro==0.1

ufork>=0.0.1

six==1.9.0

Werkzeug==0.9.4

mhashemi4• 11 years ago

they're so close to alphabetical; this is killing me

scaz• 11 years ago

This is a nice balance of the trade offs of the various concurrency primitives in Python.

Greenlets for lightweight concurrency, threads for preemptive concurrency and processes for parallelism / isolation.

SuPPort: Evented Python servers

Related Stories