On Thu, Aug 18, 2011 at 5:25 PM, Paul McMillan <[email protected]> wrote: > I added some test cases and cleaned the code up a bit. I believe sure > this solution is backwards compatible (we're adding the string > conversion, something that shouldn't have been possible before), but > I'd like input from some other people.
Looks right to me. I tried to come up with corner cases that wouldn't be backwards-compatible, but couldn't. Even if someone's got one, the previous behavior was arguably a bug anyway: a property set in __init__ shouldn't behave differently than one set later. Jacob -- 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.
