Hi! Maybe I'm a careless kind of guy, but when I test out new versions of Django, reading all of the release notes is rarely the first thing that I do... my bad. :) My first action is usually firing up the test suites and looking at the number of failed tests and deprecation warnings.
As we all know, Django-1.6 is special in this regard, since it doesn't run all the tests that the previous version would've discovered. Since it doesn't raise any deprecation warnings, it becomes really easy to assume that everything is fine and that the project is Django-1.6 ready, when in fact it is completely broken. Perhaps, Django-1.6 test runner could raise a warning and inform the user that the number of tests that would've run on the previous versions, was omitted. My wild guess is that the lack of a deprecation warning is just asking for some wildly entertaining user stories. What do you think? Best regards, Ivan -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
