How do you get rid of useless warnings?

Grant Edwards grante at visi.com
Tue Oct 7 17:00:34 CEST 2008


<rant>

I'm getting awfully tired of constant warnings about what's
going to happen at some point in the future.

Warnings like this:

  ./surfplot.py:313: Warning: 'with' will become a reserved keyword in Python 2.6

And this:

  /usr/lib/python2.5/site-packages/scipy/linalg/__init__.py:32: DeprecationWarning: NumpyTest will be removed in the next release; please update your code to use nose or unittest

And so on...
  
_I'm_not_using_Python_2.6_.  When I decided to switch to 2.6,
I'll worry about what works and doesn't work in 2.6.  In the
meantime, how do I get rid of this useless warning?  It's not
practical at this point in time to update on my production
machines the module that uses 'with' as a parameter.  Python
has been whinging at me for over a year about how 'with' is
going to become a keyword in 2.6. Yes thanks, I know.  I've
known about it for ages.  Now how do I get it to shut up about
it?

I'm also not using "the next release" of scipy, I'm using
_this_ release of scipy.  I've no clue what any of the "nose"
or "unittest" stuff is about, and it's really annoying to have
to sort through a bunch of meaningless exception messages when
I'm trying to get real work done.

I realize that every module author thinks their module is the
absolutely most important thing in the world to everybody and
all users should read hourly updates about what what the future
plans are for that module, but could you please provide an easy
way to shut off the nagging for those of us who are just trying
to get some work done with the current version...

</rant>

-- 
Grant Edwards                   grante             Yow! We are now enjoying
                                  at               total mutual interaction in
                               visi.com            an imaginary hot tub ...



More information about the Python-list mailing list