Adding Django 1.8 + Python 3 support
sfr at canb.auug.org.au
Wed Apr 8 08:25:56 AEST 2015
On Tue, 7 Apr 2015 22:39:07 +0100 Stephen Finucane <stephenfinucane at hotmail.com> wrote:
> As mentioned in the cover letter for same, patchwork support two
> now-deprecated versions of Django (1.5, 1.6). On the other hand, it
> does not yet support 1.8, which is the latest LTS version of Django.
> While it would be irresponsible to drop support for two versions of
> Django in a short time span, I suggest dropping support for version
> 1.5 followed by adding of support for 1.8. However, I have little to
> no say in this of course :)
> Similarly, Python 2.7 is now approaching five years and Python 3 has
> developed and grown in popularity during that time. The addition of
> Python 3 support is probably a good idea at this point. I've begun
> looking into this but it's going to be a lot of work and I'd like to
> know if there's demand for patches before beginning anything. I think
> the addition of tox should make testing of this a cinch. I suggest
> dropping support for Python < 2.7 (I'm unsure if 2.6 support is still
> expected (Django 1.7 doesn't support it) and I can't test it on
> Fedora 21) and adding support for Python 3.0 at the very minimum.
> What are people's opinions on the? Is there a roadmap anywhere that I
> should look at?
Just a data point: Debian Stable (Wheezy) has python-django version
1.4.5, whereas Testing (Jessie) (which will become Stable soon(?)) has
1.7.7. So Stable is already unsupported by patchwork.
Debian Stable has python version 2.7.3 and python3 version 3.2.3, while
Testing has 2.7.9 and 3.4.2 respectively.
Its probably also worth considering what is in the latest Ubuntu LTS,
RHEL and SLES releases.
Stephen Rothwell sfr at canb.auug.org.au
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the Patchwork