The low tech solution to this, may just be to have the release notes recommend running your test suite using `PYTHONWARNINGS=once`, and making sure not to swallow any output, eg. with py.test that'd be...
PYTHONWARNINGS=once py.test tests -s I'm fairly sure that making that point explicitly would save an awful lot of folks a more painful upgrade, by making it more clear how to see upcoming issues without getting bitten by them and having to debug without the help of an associated warning. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/c23e2934-b929-41b5-b3d4-572f0be8a66f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
