On Tue, Sep 25, 2012 at 7:25 AM, Jacob Kaplan-Moss <ja...@jacobian.org>wrote:
> On Tue, Sep 25, 2012 at 3:23 AM, Anssi Kääriäinen > <anssi.kaariai...@thl.fi> wrote: > > I'd like to postpone these to early next month so that I have more > > time to help in reviews and pushing some new features in. Other > > options are postponing review work, and postponing these patches to > > 1.6. > > As long as the changes are in before the beta I'm fine with it. We > need to give some time for people who're relying on those internals > (other db backends, perhaps?) to update their code, but since they're > internals and not public APIs we can relax the feature-freeze deadline > a bit. > > So as long as you can get it done before the beta, have at it. > > 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. > > 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? Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero -- 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.
