#14508: Test suite silences warnings
----------------------------------------+-----------------------------------
Reporter: lukeplant | Owner: nobody
Status: new | Milestone:
Component: Testing framework | Version: 1.2
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Comment (by russellm):
I've got a cleanup of the test suite on my to-do list just before the RC
-- a search and replace for 'failUnless'->'assertTrue',
'assertEquals'->'assertEqual' etc is easy to do, but if we do it right
now, it makes backporting tests to 1.2 a pain, since the diffs become
incompatible. If we do this just before we land 1.3, then we don't have
backporting issues to 1.2, and when we're developing 1.4, the diffs will
be minimal.
The current approach of "reset to no-pending-deprecation-warnings" only
exists because we can't retrieve the current warning state out of the
warnings module. catch_warnings helps here, except for the fact that we
can't use it in Python 2.4. If anyone can propose a way to restore old
warning state that is Python 2.4 compatible, I'm all in favor of using it.
I've tried (as best I can) to catch all the places that we need to reset
warnings, but evidently I've missed some. Specific reports are welcome,
they're not easy to find, because they depend on specfic combinations of
test ordering.
--
Ticket URL: <http://code.djangoproject.com/ticket/14508#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
