Stephen Finucane <[email protected]> writes: > On 26 Aug 16:55, Daniel Axtens wrote: >> Currently, we tox test against Python 3.4. Python 3.4 is included >> with Ubuntu 14.04, which is supported for several years to come, >> so we want to keep supporting it. >> >> However, Python 3.4 isn't included with Ubuntu 16.04, which is >> what the Docker image is based on. >> >> We could downgrade the container to 14.04, but then we'd struggle >> to get Python 3.5 into the container. Python 3.5 is the most >> recent in the Python 3 series, so we should also be supporting it. >> >> Add the apt sources for Trusty and pull in Python 3.4 from there. >> >> Signed-off-by: Daniel Axtens <[email protected]> > > I need to test this, but it looks good. Just to confirm, the aim is to > get both Python 3.4 and 3.5 on the system, correct?
Yes, that's right. I can tweak the commit message if you like. > > Stephen > >> --- >> >> This is a bit hacky, but I can't think of anything much better. >> If I downgrade to 14.04, you'd need to go through something similar >> for 3.5. We could download and build from source, but that seems >> even worse. > > No, this is definitely the best approach. I'd be curious to know how > Travis and the likes do this. I sadly know more than I would like about how Travis works. Basically they keep a big bundle of pre-built Pythons on S3 and use pyenv (think rbenv but for python) to install them and set them up. We could look into that I guess - but I'm not a big fan: I think unless we are wanting to test against a much greater range of versions we don't need the complexity yet. Regards, Daniel
signature.asc
Description: PGP signature
_______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
