> I'm against adding custom behavior in Django That's entirely reasonable, yes.
In which case, what do folks think of the following suggestions: * Linking prominently to the 'upgrading django <https://docs.djangoproject.com/en/dev/howto/upgrade-version/>' section from at the begining of every new version's release notes. * Tweaking the upgrading django section so that it recommends *first* running your existing test case with warnings enabled and resolving those at that point, *before* upgrading django, and *then* upgrading and running the tests again, at which point you don't necessarily need warnings enabled. (As it currently stands it's rather the wrong way around) * Tweaking the upgrading django section so that it also mentions making sure that your test runner isn't silencing the warning output. (eg "Using the py.test runner, you probably want to use something like `PYTHONWARNINGS=default py.test tests -s`") Cheers, Tom -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/88cc77e2-fe2b-480d-8378-9fbd33e7745a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
