Dropping support of 3.2 would potentially aid projects which have not yet converted to Python 3, since Python 3.3 supports u"Unicode Literals" but 3.2 does not. Skipping over the early 3.x versions vastly eases transition from 2.6 to 3.3.
Besides, what are the chances that someone running Python 3.n is _not_ running 3.3? -- Vernon Cole On Friday, June 28, 2013 8:17:22 AM UTC-6, Aymeric Augustin wrote: > > Hello, > > We just forked the stable/1.6.x branch. The development of Django 1.7 > starts now! > > As far as I can tell, there's a consensus on dropping support for Python > 2.6. That will allow us to remove the vendored copy of unittest2 and to > take advantage of datastructures introduced in Python 2.7 like OrderedDict. > > I think we can continue supporting Python 3.2 in addition to Python 3.3 > and 3.4. But if you see good reasons to drop it, I'd like to hear them! > > Thank you, > > -- > Aymeric. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
