News for hackers. Stuff that matters.
Re:Python Versions Used in Commercial Projects, 2016 Edition by Siecje on Friday November 11, 2016 @08:41AM (#12930495)
I'm still waiting for supervisor, beanstalkc, and cloudsigma.
Re:Python Versions Used in Commercial Projects, 2016 Edition by pingswept on Friday November 11, 2016 @10:56AM (#12931758)
The setup.py for Supervisor noted support for Python 3 starting in May of 2014: https://github.com/Supervisor/supervisor/commit/ad5cd0849a5f....

Here are the blocking issues for official support: https://github.com/Supervisor/supervisor/labels/python%203

I've been running it under Python 3 for a while with no problems.

Re:Python Versions Used in Commercial Projects, 2016 Edition by AdamN on Friday November 11, 2016 @09:32AM (#12930898)
Not sure why supervisor matters, it's just a program. It's the same thing as Homebrew running Ruby - totally doesn't matter what version they're using.
Re:Python Versions Used in Commercial Projects, 2016 Edition by mi100hael on Friday November 11, 2016 @10:11AM (#12931279)
It does if you're using their API
Re:Python Versions Used in Commercial Projects, 2016 Edition by dr_zoidberg on Friday November 11, 2016 @09:47AM (#12931043)
Of course, specific projects might not be covered, but I've seen a lot of people go "ok, just to be safe I'll use 2.7 in case down the road I get to need anything that's Py2 specific".

In your case you know exactly what your needs are, and that they're unsupported in Python 3, but I'm sure that many of those 70% Py2 projects could run just as well in Py3.

Re:Python Versions Used in Commercial Projects, 2016 Edition by poooogles on Friday November 11, 2016 @03:59PM (#12934282)
>supervisor

Can I ask why you're using supervisor instead of systemd at this point?

Re:Python Versions Used in Commercial Projects, 2016 Edition by Drdrdrq on Saturday November 12, 2016 @10:23AM (#12938254)
Can't speak for gp, but we're using supervisor inside Docker containers as lightweight init process. In our case the main advantage of Docker containers is ease of installation and consistent environment - so we don't always use just one process per container.

Systemd on the other hand is just something that is being forced down our throats. :-/