On Tue, Sep 25, 2012 at 9:48 AM, Alex Gaynor <alex.gay...@gmail.com> wrote: > My view is these things are 100% undocumented, 100% internal, anyone using > them is 100% on their on. Simply put, if we can't make changes to these APIs > without having to worry, what's the point in having a backwards > compatibility policy?
Oh, we totally can make changes, and we're pretty clear about what's supported and what's not. But given the choice, if we can not be assholes about those changes that's generally a good thing. Being nice to users is generally thought of as a good thing :) Jacob -- 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.
