I like the general idea. Going with your low tech solution we could have snippets for the X most popular test runners to treat warnings as errors. Perhaps ./manage test.py --warnings-as-errors or similar for the interface django provides. Every time django makes a release there are some that express frustration at deprecations, so making the fixing process easier can only help there.
On Thursday, 2 June 2016 22:12:54 UTC+10, Tom Christie wrote: > > 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/78834b25-d2a4-4752-af1d-580e07815302%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
