On 19 févr. 2013, at 22:56, Carl Meyer <[email protected]> wrote: > I was just about to tell someone on IRC that Django's > backwards-compatibility policy only applies to documented methods and > attributes (which is how I'd always understood it), but when I actually > went to look at the documented policy it isn't as clear as I'd hoped :/ > > https://docs.djangoproject.com/en/dev/misc/api-stability/
I said that on IRC recently, was called out, and then filed a ticket: https://code.djangoproject.com/ticket/19728 > Either way, I think it would be clearer (and more accurate to actual > practice) if we removed all mention of underscores in this document (or > even explicitly said that we don't generally use the underscore > convention), and clarified that back-compat applies only to documented > modules, classes, methods, and attributes. I agree, the docs don't reflect the current practice and should be changed. We aren't using the underscore convention (at least, not consistently). Even if we wanted to, that ship has sailed. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
