Is This Bugfix Safe?

[shanenin]

I have some output when running CDDB.py . It is ugly and I would like to remove it. I am currently running python 2.3, it is my understaning this output does not apear with python-2.4.

I get these two warnings

/usr/lib/python2.3/site-packages/DiscID.py:53: FutureWarning: x<<y losing bits or changing sign will return a long in Python 2.4 and up
  discid = ((checksum % 0xff) << 24 | total_time << 8 | last)

and this

/usr/lib/python2.3/site-packages/CDDB.py:33: FutureWarning: %u/%o/%x/%X of negative int will return a signed string in Python 2.4 and up
  query_str = (('%08lx %d ') % (disc_id, num_tracks))

if there was simple output redirection like bash uses, that would be great.

But I found these fixes, but am not sure if they will cause problems(I do not understand what is going on). Maybe you guys could help me sort them out

here is a link to the two bug fixes

http://sourceforge.net/tracker/index.php?f...833&atid=112833

any suggestions or insight would be appreciated

[iccaros]

does this show up during run or its it after the run is done?

if after then I would ignore it.. Python is just changing types on the fly (not a big deal in a small program)

if it happen while running you may what to start your progrmaing making std::err go to /dev/null to keep users from seeing it.

example

Name_Of_Script 2> /dev/null

Edited August 12, 2005 by iccaros