[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/2] Updated patches for gunicorn
From: |
Andreas Enge |
Subject: |
Re: [PATCH 0/2] Updated patches for gunicorn |
Date: |
Sun, 18 Sep 2016 11:47:30 +0200 |
User-agent: |
Mutt/1.7.0 (2016-08-17) |
On Sun, Sep 18, 2016 at 11:19:18AM +0200, Hartmut Goebel wrote:
> Well, gunicorn is a application server for running applications written
> in python. So if the application is written in Python 2, one needs to
> run the application server using Python 2, too, since it does not spawn
> a new interpreter-process [*]. This is why there are two packages.
Okay, I see. Then I would treat it as a "library" and use the
"python(2)-gunicorn" naming convention. The reason we do not do so
for applications is that in general, they appear only once in the
distribution (and generally it does not even matter that they are
written in python).
Andreas
- [PATCH 0/2] Updated patches for gunicorn, Hartmut Goebel, 2016/09/15
- [PATCH 1/2] gnu: Add gunicorn and gunicorn-python2., Hartmut Goebel, 2016/09/15
- [PATCH 2/2] gnu: Build documentation for gunicorn and gunicorn-python2., Hartmut Goebel, 2016/09/15
- Re: [PATCH 0/2] Updated patches for gunicorn, ng0, 2016/09/15
- Re: [PATCH 0/2] Updated patches for gunicorn, Andreas Enge, 2016/09/18
- Re: [PATCH 0/2] Updated patches for gunicorn, Hartmut Goebel, 2016/09/18