-----BEGIN PGP SIGNED MESSAGE-----
Jim Fulton wrote:
> I'm guessing that this has already been noticed and discussed, but
> Python 2.7 disables deprecation warnings by default.
> This will cause many tests to fail that checked that deprecation were
> This change seems likely to make Python's deprecation system useless
> and thus unused.
> I noticed this yesterday when testing a project with Python 2.7 that
> had some deprecation tests. I modified the test runner script to call:
> to renable deprecation warnings. This allowed my tests to pass and
> also, ironically, showed new useful deprecation warnings in asyncore.
> I'm not sure what the best way to handle this is. My initial thought
> is that all test runners should enable deprecations by default. This
> seems hard to enforce.
> Individual test modules can do this, but I'm uncomfortable having a
> test script make a global setting like this and the warning module
> doesn't seem to provide a way to capture the current state so it can
> be reset after running tests.
As of Python 2.6, the warnings module sports a context manager::
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -