On Fri, Jun 27, 2014 at 7:35 PM, Curtis Maloney <[email protected]> wrote:
> Am I reading this right as "people used to commonly solve this problem by > using an internal API, but now we have a public one... AND the old internal > API is now changed"? > > If so, the solution seems obvious -- document that it's time to move the > the official solution :) > Broadly speaking, I agree. However, my hesitation in categorically agreeing stems from the fact that ValidationError *is* public API. Or, at least, the constructor is, - but it seems a little absurd that we formally document a way for people to construct an object, but not to support any of the ways that they might have *used* that object. Yours, Russ Magee %-) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq848jP1E1yk16AT3_f5MyPqKA_MD1yD6W-CVQ57KD6aVCJA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
