Re: clarification of API backwards-compatibility policy

2013-02-20 Thread Jannis Leidel
On Tue, Feb 19, 2013 at 10:56 PM, Carl Meyer wrote: > Hi, > > 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

Re: clarification of API backwards-compatibility policy

2013-02-19 Thread Russell Keith-Magee
On Wed, Feb 20, 2013 at 5:56 AM, Carl Meyer wrote: > Hi, > > 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

Re: clarification of API backwards-compatibility policy

2013-02-19 Thread Aymeric Augustin
On 19 févr. 2013, at 22:56, Carl Meyer 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

Re: clarification of API backwards-compatibility policy

2013-02-19 Thread Alex Gaynor
I agree, backwards compatibility for an API should be opt-in (via documenting), not opt-out (via naming). Alex On Tue, Feb 19, 2013 at 1:56 PM, Carl Meyer wrote: > Hi, > > I was just about to tell someone on IRC that Django's > backwards-compatibility policy only applies to

clarification of API backwards-compatibility policy

2013-02-19 Thread Carl Meyer
Hi, 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 :/