Re: annoyance with Python 3.2 support in Django 1.8

[Tim Graham]

Here's a documentation proposal: https://github.com/django/django/pull/5783

On Saturday, December 5, 2015 at 6:42:18 PM UTC-5, Tim Graham wrote:
>
> No we haven't done that before. I think advertising it in the blog post 
> and release notes would be enough. In particular, I'd like to advertise it 
> as a tentative plan just in case someone comes along after we advertise the 
> plan more widely and offers a compelling reason to continue Python 3.2 
> support.
>
> On Thursday, December 3, 2015 at 8:08:12 PM UTC-5, Dan Stephenson wrote:
>>
>> Do we currently raise any warnings/exceptions in cases where Python 
>> support has / or is about to be dropped (particularly mid LTS)..   As a 
>> suggestion, I was thinking it could be helpful to people affected we raised 
>> exception msg indicating the last Django version to support their current 
>> Python version?I'd be happy to build if thought useful.
>>
>>
>>
>>
>> On Thursday, 3 December 2015 23:30:42 UTC, Chris Streeter wrote:
>>>
>>> Donald could probably provide more information, but this post from April 
>>> shows the Python 3.2 numbers downloading from PyPI are constant, and pretty 
>>> small [https://caremad.io/2015/04/a-year-of-pypi-downloads/] His take 
>>> was that CI systems (like Django's!) were doing most of the Python 3.2 
>>> package downloading.
>>>
>>> On Thu, Dec 3, 2015 at 2:18 PM, Josh Smeaton  
>>> wrote:
>>>
 I agree with Tim. Unless someone puts their hand up to say they 
 definitely require python 3.2 support for 1.8, I think it makes sense to 
 drop support in the next dot release of 1.8. 3.2 isn't an easy python to 
 find in the wild as far as I know, so I'd be surprised if there was any 
 real support for it on 1.8 by users.

 On Friday, 4 December 2015 02:50:24 UTC+11, Tim Graham wrote:
>
> No, using pypy3 doesn't make things easier. There are a handful of 
> test failures with pypy3 and it doesn't solve the issue that 
> unittest-xml-reporting doesn't work with Python 3.2.
>
> Issues aside, the main thing I'm trying to find out is, are we 
> providing any substantial value supporting Django on an unsupported 
> version 
> of Python? So far no one has indicated "yes". If you care about Django 
> security updates, shouldn't you care about Python security updates too?
>
> On Wednesday, December 2, 2015 at 5:22:46 PM UTC-5, Shai Berger wrote:
>>
>> On Wednesday 02 December 2015 21:05:00 Tim Graham wrote: 
>> > 
>> > Given that no one reading this indicated that they plan a long-term 
>> > deployment of Python 3.2, how about if in the next 1.8.x release we 
>> > advertise that Python 3.2 support for Django 1.8 will end January 
>> 1, 2017? 
>> > (we won't break anything intentionally after that, but we won't 
>> have to 
>> > worry about testing and can spin down our 12.04 machine before it's 
>> EOL a 
>> > few months later) 
>> > 
>>
>> Since you brought the issue up yourself -- shouldn't we "swap" PyPy3 
>> for 
>> Python 3.2? Would that make running tests on ubuntu 14.04 easier? 
>>
>> Just a half-baked thought, 
>>
>> Shai. 
>>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "Django developers (Contributions to Django itself)" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to django-develop...@googlegroups.com.
 To post to this group, send email to django-d...@googlegroups.com.
 Visit this group at http://groups.google.com/group/django-developers.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/django-developers/0a0631c3-4733-46fc-8884-c4050c8b8701%40googlegroups.com
  
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/f750139e-9ff7-458e-97c6-3960b127ee9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: annoyance with Python 3.2 support in Django 1.8

[Tim Graham]

No we haven't done that before. I think advertising it in the blog post and 
release notes would be enough. In particular, I'd like to advertise it as a 
tentative plan just in case someone comes along after we advertise the plan 
more widely and offers a compelling reason to continue Python 3.2 support.

On Thursday, December 3, 2015 at 8:08:12 PM UTC-5, Dan Stephenson wrote:
>
> Do we currently raise any warnings/exceptions in cases where Python 
> support has / or is about to be dropped (particularly mid LTS)..   As a 
> suggestion, I was thinking it could be helpful to people affected we raised 
> exception msg indicating the last Django version to support their current 
> Python version?I'd be happy to build if thought useful.
>
>
>
>
> On Thursday, 3 December 2015 23:30:42 UTC, Chris Streeter wrote:
>>
>> Donald could probably provide more information, but this post from April 
>> shows the Python 3.2 numbers downloading from PyPI are constant, and pretty 
>> small [https://caremad.io/2015/04/a-year-of-pypi-downloads/] His take 
>> was that CI systems (like Django's!) were doing most of the Python 3.2 
>> package downloading.
>>
>> On Thu, Dec 3, 2015 at 2:18 PM, Josh Smeaton  wrote:
>>
>>> I agree with Tim. Unless someone puts their hand up to say they 
>>> definitely require python 3.2 support for 1.8, I think it makes sense to 
>>> drop support in the next dot release of 1.8. 3.2 isn't an easy python to 
>>> find in the wild as far as I know, so I'd be surprised if there was any 
>>> real support for it on 1.8 by users.
>>>
>>> On Friday, 4 December 2015 02:50:24 UTC+11, Tim Graham wrote:

 No, using pypy3 doesn't make things easier. There are a handful of test 
 failures with pypy3 and it doesn't solve the issue that 
 unittest-xml-reporting doesn't work with Python 3.2.

 Issues aside, the main thing I'm trying to find out is, are we 
 providing any substantial value supporting Django on an unsupported 
 version 
 of Python? So far no one has indicated "yes". If you care about Django 
 security updates, shouldn't you care about Python security updates too?

 On Wednesday, December 2, 2015 at 5:22:46 PM UTC-5, Shai Berger wrote:
>
> On Wednesday 02 December 2015 21:05:00 Tim Graham wrote: 
> > 
> > Given that no one reading this indicated that they plan a long-term 
> > deployment of Python 3.2, how about if in the next 1.8.x release we 
> > advertise that Python 3.2 support for Django 1.8 will end January 1, 
> 2017? 
> > (we won't break anything intentionally after that, but we won't have 
> to 
> > worry about testing and can spin down our 12.04 machine before it's 
> EOL a 
> > few months later) 
> > 
>
> Since you brought the issue up yourself -- shouldn't we "swap" PyPy3 
> for 
> Python 3.2? Would that make running tests on ubuntu 14.04 easier? 
>
> Just a half-baked thought, 
>
> Shai. 
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Django developers (Contributions to Django itself)" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to django-develop...@googlegroups.com.
>>> To post to this group, send email to django-d...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/django-developers.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/django-developers/0a0631c3-4733-46fc-8884-c4050c8b8701%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/5d501c8f-a413-4854-bfae-d3d63159c144%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: annoyance with Python 3.2 support in Django 1.8

[Dan Stephenson]

Do we currently raise any warnings/exceptions in cases where Python support 
has / or is about to be dropped (particularly mid LTS)..   As a suggestion, 
I was thinking it could be helpful to people affected we raised exception 
msg indicating the last Django version to support their current Python 
version?I'd be happy to build if thought useful.




On Thursday, 3 December 2015 23:30:42 UTC, Chris Streeter wrote:
>
> Donald could probably provide more information, but this post from April 
> shows the Python 3.2 numbers downloading from PyPI are constant, and pretty 
> small [https://caremad.io/2015/04/a-year-of-pypi-downloads/] His take was 
> that CI systems (like Django's!) were doing most of the Python 3.2 package 
> downloading.
>
> On Thu, Dec 3, 2015 at 2:18 PM, Josh Smeaton  > wrote:
>
>> I agree with Tim. Unless someone puts their hand up to say they 
>> definitely require python 3.2 support for 1.8, I think it makes sense to 
>> drop support in the next dot release of 1.8. 3.2 isn't an easy python to 
>> find in the wild as far as I know, so I'd be surprised if there was any 
>> real support for it on 1.8 by users.
>>
>> On Friday, 4 December 2015 02:50:24 UTC+11, Tim Graham wrote:
>>>
>>> No, using pypy3 doesn't make things easier. There are a handful of test 
>>> failures with pypy3 and it doesn't solve the issue that 
>>> unittest-xml-reporting doesn't work with Python 3.2.
>>>
>>> Issues aside, the main thing I'm trying to find out is, are we providing 
>>> any substantial value supporting Django on an unsupported version of 
>>> Python? So far no one has indicated "yes". If you care about Django 
>>> security updates, shouldn't you care about Python security updates too?
>>>
>>> On Wednesday, December 2, 2015 at 5:22:46 PM UTC-5, Shai Berger wrote:

 On Wednesday 02 December 2015 21:05:00 Tim Graham wrote: 
 > 
 > Given that no one reading this indicated that they plan a long-term 
 > deployment of Python 3.2, how about if in the next 1.8.x release we 
 > advertise that Python 3.2 support for Django 1.8 will end January 1, 
 2017? 
 > (we won't break anything intentionally after that, but we won't have 
 to 
 > worry about testing and can spin down our 12.04 machine before it's 
 EOL a 
 > few months later) 
 > 

 Since you brought the issue up yourself -- shouldn't we "swap" PyPy3 
 for 
 Python 3.2? Would that make running tests on ubuntu 14.04 easier? 

 Just a half-baked thought, 

 Shai. 

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-develop...@googlegroups.com .
>> To post to this group, send email to django-d...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/django-developers.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/0a0631c3-4733-46fc-8884-c4050c8b8701%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/933a22e5-3f88-4663-b25a-9fdedc83d9c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: annoyance with Python 3.2 support in Django 1.8

[Chris Streeter]

Donald could probably provide more information, but this post from April
shows the Python 3.2 numbers downloading from PyPI are constant, and pretty
small [https://caremad.io/2015/04/a-year-of-pypi-downloads/] His take was
that CI systems (like Django's!) were doing most of the Python 3.2 package
downloading.

On Thu, Dec 3, 2015 at 2:18 PM, Josh Smeaton  wrote:

> I agree with Tim. Unless someone puts their hand up to say they definitely
> require python 3.2 support for 1.8, I think it makes sense to drop support
> in the next dot release of 1.8. 3.2 isn't an easy python to find in the
> wild as far as I know, so I'd be surprised if there was any real support
> for it on 1.8 by users.
>
> On Friday, 4 December 2015 02:50:24 UTC+11, Tim Graham wrote:
>>
>> No, using pypy3 doesn't make things easier. There are a handful of test
>> failures with pypy3 and it doesn't solve the issue that
>> unittest-xml-reporting doesn't work with Python 3.2.
>>
>> Issues aside, the main thing I'm trying to find out is, are we providing
>> any substantial value supporting Django on an unsupported version of
>> Python? So far no one has indicated "yes". If you care about Django
>> security updates, shouldn't you care about Python security updates too?
>>
>> On Wednesday, December 2, 2015 at 5:22:46 PM UTC-5, Shai Berger wrote:
>>>
>>> On Wednesday 02 December 2015 21:05:00 Tim Graham wrote:
>>> >
>>> > Given that no one reading this indicated that they plan a long-term
>>> > deployment of Python 3.2, how about if in the next 1.8.x release we
>>> > advertise that Python 3.2 support for Django 1.8 will end January 1,
>>> 2017?
>>> > (we won't break anything intentionally after that, but we won't have
>>> to
>>> > worry about testing and can spin down our 12.04 machine before it's
>>> EOL a
>>> > few months later)
>>> >
>>>
>>> Since you brought the issue up yourself -- shouldn't we "swap" PyPy3 for
>>> Python 3.2? Would that make running tests on ubuntu 14.04 easier?
>>>
>>> Just a half-baked thought,
>>>
>>> Shai.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/0a0631c3-4733-46fc-8884-c4050c8b8701%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAJYyoGFpJ7VCfODUy9QRf%3DNBjw_XbBLxn02PVmdNZV_bdiy4qg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: annoyance with Python 3.2 support in Django 1.8

[Josh Smeaton]

I agree with Tim. Unless someone puts their hand up to say they definitely 
require python 3.2 support for 1.8, I think it makes sense to drop support 
in the next dot release of 1.8. 3.2 isn't an easy python to find in the 
wild as far as I know, so I'd be surprised if there was any real support 
for it on 1.8 by users.

On Friday, 4 December 2015 02:50:24 UTC+11, Tim Graham wrote:
>
> No, using pypy3 doesn't make things easier. There are a handful of test 
> failures with pypy3 and it doesn't solve the issue that 
> unittest-xml-reporting doesn't work with Python 3.2.
>
> Issues aside, the main thing I'm trying to find out is, are we providing 
> any substantial value supporting Django on an unsupported version of 
> Python? So far no one has indicated "yes". If you care about Django 
> security updates, shouldn't you care about Python security updates too?
>
> On Wednesday, December 2, 2015 at 5:22:46 PM UTC-5, Shai Berger wrote:
>>
>> On Wednesday 02 December 2015 21:05:00 Tim Graham wrote: 
>> > 
>> > Given that no one reading this indicated that they plan a long-term 
>> > deployment of Python 3.2, how about if in the next 1.8.x release we 
>> > advertise that Python 3.2 support for Django 1.8 will end January 1, 
>> 2017? 
>> > (we won't break anything intentionally after that, but we won't have to 
>> > worry about testing and can spin down our 12.04 machine before it's EOL 
>> a 
>> > few months later) 
>> > 
>>
>> Since you brought the issue up yourself -- shouldn't we "swap" PyPy3 for 
>> Python 3.2? Would that make running tests on ubuntu 14.04 easier? 
>>
>> Just a half-baked thought, 
>>
>> Shai. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/0a0631c3-4733-46fc-8884-c4050c8b8701%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: annoyance with Python 3.2 support in Django 1.8

[Tim Graham]

No, using pypy3 doesn't make things easier. There are a handful of test 
failures with pypy3 and it doesn't solve the issue that 
unittest-xml-reporting doesn't work with Python 3.2.

Issues aside, the main thing I'm trying to find out is, are we providing 
any substantial value supporting Django on an unsupported version of 
Python? So far no one has indicated "yes". If you care about Django 
security updates, shouldn't you care about Python security updates too?

On Wednesday, December 2, 2015 at 5:22:46 PM UTC-5, Shai Berger wrote:
>
> On Wednesday 02 December 2015 21:05:00 Tim Graham wrote: 
> > 
> > Given that no one reading this indicated that they plan a long-term 
> > deployment of Python 3.2, how about if in the next 1.8.x release we 
> > advertise that Python 3.2 support for Django 1.8 will end January 1, 
> 2017? 
> > (we won't break anything intentionally after that, but we won't have to 
> > worry about testing and can spin down our 12.04 machine before it's EOL 
> a 
> > few months later) 
> > 
>
> Since you brought the issue up yourself -- shouldn't we "swap" PyPy3 for 
> Python 3.2? Would that make running tests on ubuntu 14.04 easier? 
>
> Just a half-baked thought, 
>
> Shai. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/cfb4a4e9-c415-4c67-8408-7440a7c314f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: annoyance with Python 3.2 support in Django 1.8

[Shai Berger]

On Wednesday 02 December 2015 21:05:00 Tim Graham wrote:
> 
> Given that no one reading this indicated that they plan a long-term
> deployment of Python 3.2, how about if in the next 1.8.x release we
> advertise that Python 3.2 support for Django 1.8 will end January 1, 2017?
> (we won't break anything intentionally after that, but we won't have to
> worry about testing and can spin down our 12.04 machine before it's EOL a
> few months later)
> 

Since you brought the issue up yourself -- shouldn't we "swap" PyPy3 for 
Python 3.2? Would that make running tests on ubuntu 14.04 easier?

Just a half-baked thought,

Shai.

Re: annoyance with Python 3.2 support in Django 1.8

[Tim Graham]

I ran into another snag trying to put the Python 3.2 tests on the 14.04 
machines and that's that the unittest-xml-reporting package we use on 
Jenkins to collect the test results isn't compatible with Python 3.2 (the 
Ubuntu 12.04 machine uses an older fork of unittest-xml-reporting but I 
removed that hack on the 14.04 machines). Maybe I could find an older 
official version of unittest-xml-reporting that would work, but I don't 
think I'm adding any value with this exercise.

Given that no one reading this indicated that they plan a long-term 
deployment of Python 3.2, how about if in the next 1.8.x release we 
advertise that Python 3.2 support for Django 1.8 will end January 1, 2017? 
(we won't break anything intentionally after that, but we won't have to 
worry about testing and can spin down our 12.04 machine before it's EOL a 
few months later) 

On Thursday, November 26, 2015 at 9:53:51 AM UTC-5, Donald Stufft wrote:
>
>
> On Nov 26, 2015, at 9:50 AM, Tim Graham  
> wrote:
>
> The thing that makes me a little uncomfortable is promoting the use of 
> possibly insecure Python 3.2 well after it's end-of-life. I guess there 
> might be some Linux distributions that will backport security fixes to 
> their own versions of Python 3.2, but it seems that Ubuntu 12.04's version 
> of Python 3.2 didn't incorporate the security fix which caused breakage.
>
>
> FTR the next major version of pip does not support Python 3.2.
>
> -
> Donald Stufft
> PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 
> DCFA 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/cff4be08-fcb7-40dc-b450-0392bade6482%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: annoyance with Python 3.2 support in Django 1.8

[Donald Stufft]

> On Nov 26, 2015, at 9:50 AM, Tim Graham  wrote:
> 
> The thing that makes me a little uncomfortable is promoting the use of 
> possibly insecure Python 3.2 well after it's end-of-life. I guess there might 
> be some Linux distributions that will backport security fixes to their own 
> versions of Python 3.2, but it seems that Ubuntu 12.04's version of Python 
> 3.2 didn't incorporate the security fix which caused breakage.


FTR the next major version of pip does not support Python 3.2.

-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/247186BB-8325-4418-9046-AAA5E6C9711D%40stufft.io.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: annoyance with Python 3.2 support in Django 1.8

[Tim Graham]

The thing that makes me a little uncomfortable is promoting the use of 
possibly insecure Python 3.2 well after it's end-of-life. I guess there 
might be some Linux distributions that will backport security fixes to 
their own versions of Python 3.2, but it seems that Ubuntu 12.04's version 
of Python 3.2 didn't incorporate the security fix which caused breakage.

Is there anyone reading this planning a long-term deployment of Python 3.2? 
If so, how long?

Yes, we could mark the tests as expected failure if needed.

On Thursday, November 26, 2015 at 9:36:32 AM UTC-5, Aymeric Augustin wrote:
>
> Hello Tim,
>
> Did you consider marking affected tests as expected failures on Python 
> 3.2.6?
>
> I've done that on one of my projects which faced this exact issue (or a 
> closely related one):
>
> https://github.com/aaugustin/myks-gallery/blob/master/gallery/test_admin.py#L199-L205
>
> Best regards,
>
> -- 
> Aymeric.
>
> 2015-11-26 1:36 GMT+01:00 Tim Graham :
>
>> Django 1.8 is the last version to support Python 3.2. Python 3.2 is 
>> scheduled to be end of life at February 2016 [1] while Django 1.8 is 
>> scheduled to be supported until April 2018. The latest security release for 
>> the 3.2 series, Python 3.2.6 contained a regression that causes 30 admin 
>> test failures in the Django test suite related to parsing of httponly 
>> cookies. I'm not sure if this problem is limited to the test client or if 
>> it has the potential to cause problems in a web server context (if anyone 
>> is using Python 3.2.6, I'd be interested to know). I submitted a patch to 
>> Python to correct the issue [2], but it appears unlikely that the patch 
>> will be applied along with a new release (no response from Python 3.2 
>> release manager in 1 year).
>>
>> Due to the test failures, we cannot run the Django test suite with Python 
>> 3.2 on the Ubuntu 14.04 CI machines which use the deadsnakes PPA [3] to 
>> install the latest version of Python (3.2.6). Therefore the tests are 
>> limited to running on our one remaining Ubuntu 12.04 CI machine which 
>> includes Python 3.2.3 (deadsnakes doesn't bundle versions of Python that 
>> would override the one included by the distribution). Support for Ubuntu 
>> 12.04 ends April 2017, so we shouldn't keep that machine longer than that.
>>
>> Options:
>> 1. Drop Python 3.2 support for Django 1.8 sometime before Django 1.8 EOL
>> 2. Keep Python 3.2 support until Django 1.8 EOL:
>>   a. Don't worry about CI support and rely on local testing of security 
>> fixes (we had the same situation with Django 1.4 and Python 2.5)
>>   b. Install the latest non-broken Python 3.2 release (3.2.5) "manually" 
>> (without using deadsnakes) on the newer CI servers
>> 3. Your idea
>>
>> Thanks for your feedback!
>>
>> [1] https://www.python.org/dev/peps/pep-0392/
>> [2] https://bugs.python.org/issue22758
>> [3] https://launchpad.net/~fkrull/+archive/ubuntu/deadsnakes
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-develop...@googlegroups.com .
>> To post to this group, send email to django-d...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/django-developers.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/34dd15c4-dba5-46fe-9ac0-6d5a426db2df%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Aymeric.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/93c64bac-07e6-4ed4-ac9e-f54dc5f927ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: annoyance with Python 3.2 support in Django 1.8

[Aymeric Augustin]

Hello Tim,

Did you consider marking affected tests as expected failures on Python
3.2.6?

I've done that on one of my projects which faced this exact issue (or a
closely related one):
https://github.com/aaugustin/myks-gallery/blob/master/gallery/test_admin.py#L199-L205

Best regards,

-- 
Aymeric.

2015-11-26 1:36 GMT+01:00 Tim Graham :

> Django 1.8 is the last version to support Python 3.2. Python 3.2 is
> scheduled to be end of life at February 2016 [1] while Django 1.8 is
> scheduled to be supported until April 2018. The latest security release for
> the 3.2 series, Python 3.2.6 contained a regression that causes 30 admin
> test failures in the Django test suite related to parsing of httponly
> cookies. I'm not sure if this problem is limited to the test client or if
> it has the potential to cause problems in a web server context (if anyone
> is using Python 3.2.6, I'd be interested to know). I submitted a patch to
> Python to correct the issue [2], but it appears unlikely that the patch
> will be applied along with a new release (no response from Python 3.2
> release manager in 1 year).
>
> Due to the test failures, we cannot run the Django test suite with Python
> 3.2 on the Ubuntu 14.04 CI machines which use the deadsnakes PPA [3] to
> install the latest version of Python (3.2.6). Therefore the tests are
> limited to running on our one remaining Ubuntu 12.04 CI machine which
> includes Python 3.2.3 (deadsnakes doesn't bundle versions of Python that
> would override the one included by the distribution). Support for Ubuntu
> 12.04 ends April 2017, so we shouldn't keep that machine longer than that.
>
> Options:
> 1. Drop Python 3.2 support for Django 1.8 sometime before Django 1.8 EOL
> 2. Keep Python 3.2 support until Django 1.8 EOL:
>   a. Don't worry about CI support and rely on local testing of security
> fixes (we had the same situation with Django 1.4 and Python 2.5)
>   b. Install the latest non-broken Python 3.2 release (3.2.5) "manually"
> (without using deadsnakes) on the newer CI servers
> 3. Your idea
>
> Thanks for your feedback!
>
> [1] https://www.python.org/dev/peps/pep-0392/
> [2] https://bugs.python.org/issue22758
> [3] https://launchpad.net/~fkrull/+archive/ubuntu/deadsnakes
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/34dd15c4-dba5-46fe-9ac0-6d5a426db2df%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Aymeric.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CANE-7mWHSKZfjpo-5BH40-kZVF%2BXq-TYo2cCeLPpiegbmbJN8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: annoyance with Python 3.2 support in Django 1.8

[Raphael Michel]

Hi,

Am Wed, 25 Nov 2015 16:36:52 -0800 (PST)
schrieb Tim Graham :
> b. Install the latest non-broken Python 3.2 release (3.2.5)
> "manually" (without using deadsnakes) on the newer CI servers

While it would only really hurt the people in charge with the bugfix
releases, as Django 1.8 will be around for another 2.5 years, I think
dropping CI is not a good idea, considering that is comparatively easy
to compile specific python versions by oneself.

However, we should definitely document somewhere that there are
possbile unknown problems with 3.2.6 and the django admin.

Cheers
Raphael

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/20151126152618.2f4dba63%40kvothe.
For more options, visit https://groups.google.com/d/optout.


pgpBiht4aGxUy.pgp
Description: Digitale Signatur von OpenPGP

Re: annoyance with Python 3.2 support in Django 1.8

[Aymeric Augustin]

2015-11-26 5:22 GMT+01:00 Asif Saifuddin :

> Python 3.2 should be removed as if any one use py3 should use 3.3+ or
> better the latest stable.
>

Hi Asif,

Your email sounds like the answer is obvious. It doesn't show that you
thought about the use cases, especially those you don't have yourself and
may be less familiar with. As such it's hard to take it at face value.

More generally, I've noticed that your contributions, either on this
mailing list or on the bug tracker, tend to be very terse, not to bring new
information, and not to be open for further debate. You'll be more
convincing if you show that you took the time to understand the problem at
hand and explain why you suggest a trade-off. When a question is being
debated, there are usually at least two sides and any choice results from a
trade-off e.g. X matters, but Y matters more.

Thanks,

-- 
Aymeric.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CANE-7mVENF9ht%3DwoEZccYQyBCOwAsTKKfUm1%3DWVeV_PcZONdMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: annoyance with Python 3.2 support in Django 1.8

[Asif Saifuddin]

Python 3.2 should be removed as if any one use py3 should use 3.3+ or 
better the latest stable.

best

Asif

On Thursday, November 26, 2015 at 6:36:53 AM UTC+6, Tim Graham wrote:
>
> Django 1.8 is the last version to support Python 3.2. Python 3.2 is 
> scheduled to be end of life at February 2016 [1] while Django 1.8 is 
> scheduled to be supported until April 2018. The latest security release for 
> the 3.2 series, Python 3.2.6 contained a regression that causes 30 admin 
> test failures in the Django test suite related to parsing of httponly 
> cookies. I'm not sure if this problem is limited to the test client or if 
> it has the potential to cause problems in a web server context (if anyone 
> is using Python 3.2.6, I'd be interested to know). I submitted a patch to 
> Python to correct the issue [2], but it appears unlikely that the patch 
> will be applied along with a new release (no response from Python 3.2 
> release manager in 1 year).
>
> Due to the test failures, we cannot run the Django test suite with Python 
> 3.2 on the Ubuntu 14.04 CI machines which use the deadsnakes PPA [3] to 
> install the latest version of Python (3.2.6). Therefore the tests are 
> limited to running on our one remaining Ubuntu 12.04 CI machine which 
> includes Python 3.2.3 (deadsnakes doesn't bundle versions of Python that 
> would override the one included by the distribution). Support for Ubuntu 
> 12.04 ends April 2017, so we shouldn't keep that machine longer than that.
>
> Options:
> 1. Drop Python 3.2 support for Django 1.8 sometime before Django 1.8 EOL
> 2. Keep Python 3.2 support until Django 1.8 EOL:
>   a. Don't worry about CI support and rely on local testing of security 
> fixes (we had the same situation with Django 1.4 and Python 2.5)
>   b. Install the latest non-broken Python 3.2 release (3.2.5) "manually" 
> (without using deadsnakes) on the newer CI servers
> 3. Your idea
>
> Thanks for your feedback!
>
> [1] https://www.python.org/dev/peps/pep-0392/
> [2] https://bugs.python.org/issue22758
> [3] https://launchpad.net/~fkrull/+archive/ubuntu/deadsnakes
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/bfc650af-6c28-4bc3-b792-5ae212accdb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.