On 06/09/12 19:09, Aymeric Augustin wrote: > Now we have two alternatives: > 1) tell them to roll their own compat or wait until they can target 1.5 > + 1.6 — quite a downer, > 2) add some forwards compatibility tools to 1.4. > > We generally don't add features to minor releases, but there's a > precedent (csrf_noop), and the patch is as harmless as they come (see > attachment). > > What do you think?
This was something I was going to bring up myself, since it is a major obstacle to re-usable django apps actually providing Python 3 compatibility. I'm +1 on adding forwards compatibility to 1.4.X, assuming a safe patch. Luke -- "In your presence there is fullness of joy; at your right hand are pleasures forevermore" Psalm 16:11 Luke Plant || http://lukeplant.me.uk/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
