On Tue, 14 Oct 2014, Brian May wrote: > So to me it looks like loaddata is generating 1 warning, when we were > hoping for no warnings.
Thanks for the initial analysis. I forwarded a bug to Django: https://code.djangoproject.com/ticket/23651 > Now I am a bit puzzled as to (a) why this didn't occur previously or on > wheezy, and (b) why it only happens with Python3. [...] > One mystery resolved. Not really: > Under python2, the fixture_name contains u'initial_data', so the if > condition fails. $ python Python 2.7.8 (default, Oct 7 2014, 17:59:21) [GCC 4.9.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> 'initial_data' == u'initial_data' True I traced the code and we get to the same point: warnings.warn(..., RemovedInDjango19Warning) is called both with Python 2 and Python 3. But with Python 3 it's caught by catch_warnings() but not with Python 2, possibly due to a bug in Python: http://bugs.python.org/issue4180 (that bug has been identified by a Django core developer on the ticket above) > Still not sure why this only recently became an issue in unstable. Because the above bug has been fixed in python 3.4.2 which has been uploaded recently. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org