On Thursday 20 December 2012, Karen Tracey wrote:
> This has come up before, see: https://code.djangoproject.com/ticket/17974
>
Figures...
> 1.3 is security-fix only at this point,
Yes, and pretty close to not-even-security-fix; I'm well aware of that, and
that's why I wrote:
> > The issue for this call is moot now, but there may be others like it.
and...
> we'd have to make a pretty big
> exception to put anything into 1.3 to warn users of their mis-use of an
> undocumented parameter to distinct....
>
I didn't think this was a valid bug. I was trying to make the point that, in
general,
* when intorducing a call in the development branch,
* which, if used mistakenly on a maintenance branch, would "work",
* that is, not do the new functionality, but not raise an exception,
* then it is worthwhile to put a warning in the maintenance branch.
Sorry if I wasn't clear,
Shai.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
