Bug#768117: debian-policy: WSGI API must distinguish between Python 2 and 3
On Wed, Nov 05, 2014 at 02:38:39PM +1100, Brian May wrote:
> Package: debian-policy
> Severity: normal
>
> The httpd-wsgi virtual name was added in response to #588497.
>
> However, as per the following email:
>
> https://lists.debian.org/debian-devel/2014/09/msg00719.html
>
> "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."
>
> This means, as currently written, Python2 packages that depend on
> httpd-wsgi might get a Python3 implementation of WSGI, which won't work.
>
> Similarly, Python3 packages that depend on httpd-wsgi might get a
> Python2 implementation of WSGI which also won't work.
>
> We need two virtual package names, one for Python2 and one for Python3.
What I am unclear is why a single virtual package httpd-wsgi3 will work
for python 3.2, 3.3, 3.4 etc.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: