With as many new frameworks as there are out there, with the gains in popularity seen in Go and Node, my thinking is, move quickly, break (some very small) things, or die slowly. As was said, if your favorite lib doesn't work with 1.6 or 1.7, either use a prior version, or spend some time contributing the 10 minutes to 2 hours that most of these changes would take at most. You'll feel good about it. You'll feel less frustrated, and you'll understand, thereafter, what it means to be an active part of the community. I too used to be a rail bird. It gets you "exactly nowhere", in the words of Russell K.M., and it makes those who contribute feel unappreciated.
-- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ec509e6c-c72c-43f8-8d2d-eebc87347958%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
