On Tuesday, May 16, 2017 03:42:52 PM Michael Hudson-Doyle wrote:
> I have not, no. I guess we'll get the autopkgtest coverage when Python 3.6
> is the default, perhaps I should try something before then...
I have a vague recollection I looked at this before and it's more complicated
than that.
On Tuesday, May 16, 2017 03:11:33 PM Michael Hudson-Doyle wrote:
> I don't think that's quite right, I think the problem is the computation of
> PY3MIN and PY3MAX. I've uploaded this patch to Ubuntu which I think fixes
> the problem:
>
I have not, no. I guess we'll get the autopkgtest coverage when Python 3.6
is the default, perhaps I should try something before then...
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
I don't think that's quite right, I think the problem is the computation of
PY3MIN and PY3MAX. I've uploaded this patch to Ubuntu which I think fixes
the problem:
http://launchpadlibrarian.net/319819189/mod-wsgi_4.5.11-1build1_4.5.11-1ubuntu1.diff.gz
(you'd still have to edit wsgi.load to use the
Package: src:mod-wsgi
Version: 4.5.11-1
Tags: sid buster
User: debian-pyt...@lists.debian.org
Usertags: python3.6
mod-wsgi only supports the default python/python3 version, therefore the build
dependencies should be limited to the default versions (s/-all//g).
5 matches
Mail list logo