I updated the syncdb tests as well since it was straightforward. I get a clean output on Python 2.7. Python 3 still has some issues (e.g. #19905), but these aren't deprecated features.
On Tuesday, September 3, 2013 8:46:30 AM UTC-4, Tim Graham wrote: > > Thanks for raising the issue. I think I committed the first and last of > the three, so I'll fix those. > > I've also added a ticket to document "how to deprecate a feature" in order > to make these guidelines more accessible. > > https://code.djangoproject.com/ticket/21024 > > On Monday, September 2, 2013 8:41:46 PM UTC-4, Ramiro Morales wrote: >> >> On Mon, Sep 2, 2013 at 8:08 AM, Aymeric Augustin >> <[email protected]> wrote: >> > Hello, >> > >> > When a feature is deprecated, it raises a PendingDeprecationWarning, >> either at import time or at run time. After the following release it raises >> DeprecationWarning. Assuming we have a good test coverage, these warnings >> will be shown by the test suite, with -Wall for PendingDeprecationWarning, >> by default for DeprecationWarning. This is annoying. The output of the test >> suite should remain clean. >> > >> > Unfortunately, I've noticed that we often forget to silence warnings >> when we deprecate a feature. For instance, right new, the test suite raises >> warnings related to custom SQL, syncdb, and SortedDict (with -Wall). If >> you committed one of these deprecations, would you mind silencing the >> PendingDeprecationWarnings in the tests? >> > >> > There are two ways to achieve that: >> > [...] >> >> Thanks Aymeric for raising awareness about the problem and the compact >> action item description. >> >> I plan to propose some changes that involve a deprecation cycle and >> had some vague recollection about an email or ticket about the same >> issue by Carl but had been unable to find it. Your mail made me search >> again and luckily this time I could find it: >> https://code.djangoproject.com/ticket/17049 -- Fortunately, the >> recommended solution there is in the same spirit as yours. >> >> A result of that ticket is the fact that our CI setup uses -Wall so we >> can see these warnings at the console output of every configuration >> e.g.: >> >> >> http://ci.djangoproject.com/job/Django/database=postgres,python=python3.3/lastBuild/console >> >> >> Regards, >> >> -- >> Ramiro Morales >> @ramiromorales >> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
