On 25 Nov 17:45, Mauro Carvalho Chehab wrote: [snip]
> > I'd love to get a few of these patches, should you have the time/inclination > > to release them (either via patches or a public Git). I won't re-add Django > > 1.4/1.5 support myself, but if someone has the work done and it's > > zero-effort > > to integrate them then I'd certainly consider this. > > We're upgrading our servers to the latest Debian LTS (version 8.2). > > It comes with Django 1.7.7, but only for Python 3: > $ dpkg -p python3-django > Package: python3-django > Priority: optional > Section: python > Installed-Size: 15654 > Maintainer: Debian Python Modules Team > <python-modules-t...@lists.alioth.debian.org> > Architecture: all > Source: python-django > Version: 1.7-2~bpo70+1 > Depends: python3 (>= 3.2.3-3~), python-django-common (= 1.7-2~bpo70+1) > > The latest version of Django for Python 2.7 is 1.4.5: > $ dpkg -p python-django > Package: python-django > Priority: optional > Section: python > Installed-Size: 51004 > Maintainer: Chris Lamb <la...@debian.org> > Architecture: all > Version: 1.4.5-1+deb7u8 > Depends: python (>= 2.6.6-7~), python (<< 2.8) > > It seems, however, that patchwork doesn't work yet with Python 3, > right? If so, we should stick with patchwork running with Django 1.4, > or make patchwork to work also with python3. See: https://lists.ozlabs.org/pipermail/patchwork/2015-November/002172.html. If you have time to review, I'd be very grateful for any input you might offer. [snip] > > > True. The autodelegation patches were not sent upstream because upstream > > > has changed the Django's requirements, and we weren't unable to rebase > > > to the newer version, due to the LTS requirements. > > I ported the autodelegation patches to the latest version of patchwork, > but I'm unable to test (because of the conflict mismatch between python > and django). > > If you want, I may submit those untested patches, in the hope that > someone would test them before applying. Seeing as we now have Python 3 patches, what are the possibilities of doing some of this testing yourself? :) If this isn't possible then I'll get to it eventually, but I'd really like to focus on expanding test coverage so I can maximise the chances of catching any remaining Python 3 issues. Cheers, Stephen _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork