Re: apache2 issues

Cc: debian developers <debian-devel@lists.debian.org>

Subject: Re: apache2 issues

From: Brian May <brian@microcomaustralia.com.au>

Date: Mon, 6 Oct 2014 13:31:16 +1100

Message-id: <[🔎] CAA0ZO6DByBZ5j4wWnGYwfSepGb2FJiziQ9eiSYWk8NH6HcD7bA@mail.gmail.com>

In-reply-to: <87wq8uhio5.wl%jeroen@dekkers.ch>

References: <CAA0ZO6BU=+k90_nASaDf_hCAVFaweRyJ8hD27DSJmSsxnzL5sQ@mail.gmail.com> <3142909.HlM5nLrZUK@grep.be> <53D73903.6090106@free.fr> <3410912.of5nXUqjGV@grep.be> <CAA0ZO6BHOmOX6yfG7e6YyrhdkbTJoqSM=3YZv0b0pkowyKA5iQ@mail.gmail.com> <878unco7rv.wl%jeroen@dekkers.ch> <CAA0ZO6ASAHuJQWryus5-+x3EkknO=qOKgHQcnTHA_KmBxsgt8Q@mail.gmail.com> <20140923065156.3279.88444@bastian.jones.dk> <87wq8uhio5.wl%jeroen@dekkers.ch>

On 23 September 2014 17:58, Jeroen Dekkers <jeroen@dekkers.ch> wrote:

> Isn't that an implementation detail? Is Python version relevant for the
> on-the-wire WSGI protocol?

WSGI is an API, not a wire protocol. The Python version of the WSGI
server would also be the Python version the code is run under, so we
must distinguish between Python 2 and 3. The best way would probably
be to specify that httpd-wsgi is for Python 2 and create a httpd-wsgi3
virtual package for Python 3.

How do we make this change? Does this require reopening #588497 and/or creating a new bug against debian-policy?

--
Brian May <brian@microcomaustralia.com.au>

Reply to: