> I'd prefer backwards compatibility. The way I'm envisioning it would > complicate the code a bit, but I think preserving compatibility is > worth it:
It would be nice to keep backwards compat, for the sole reason that the quickest way to test your code against a django upgrade is to run tests - it would be ideal to migrate to 1.1 without having to refactor any tests just to get there. OTOH, I don't think it would be a huge deal to not preserve backwards compat - in the worst case scenario, users can simply comment out the offending code temporarily, and although backwards compat is emphasized from 1.0 on I think there would be some leeway with a fairly specific test feature. The worst situation would be buggy test code, so if it turns out to be very complicated to maintain backwards compat, we should leave it behind. -rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
