#726 APItest/Twisted FutureWarnings

[Thomas Naughton]

The APItest tools uses the TwistedMatrix libraries and
there is a warning generated from the current version
of Twisted shipped with oscar-4.2beta. This is only a
warning and not an error. I had planned on upgrading
APItest and using the newer Twisted RPMS that Will has
available, but not until after the oscar-4.2 release.
I believe that should remove this warning msg by using
a newer version of Twisted.

Example Warning message:

/usr/lib/python2.3/site-packages/twisted/internet/defer.py:398:
FutureWarning: h
ex()/oct() of negative int will return a signed string
in Python 2.4 and up
return "<%s at %s>" % (cname, hex(id(self)))

[Thomas Naughton]

Logged In: YES
user_id=288102

Note, a work around would be to call the python interpreter
directly, and add a "-W" command line option to ignore this
FutureWarning.

Example:
cd packages/pvm/testing/
python -W ignore::FutureWarning:: \ /usr/local/apitest/apitest -T -f install_tests.apb

This would be a workaround until we have the updated Twisted
libs, etc. (hopefully) for 5.0 but if not ready/willing then
this work around could be added to the testing driver
script(s) whereever apitest is being called.

Food for thought.

[Thomas Naughton]

Logged In: YES
user_id=288102

When I get time, I should upgrade APItest to 1.0.0 and use
the newer RPMS from sss-oscar-2.0 for Twisted, TwistedWeb,
ZopeInterfaces and python-elementtree (where necessary).

This will fix the future warnings and give us a *newer*
version of APItest.

[Thomas Naughton]

Logged In: YES
user_id=288102

Updated to APItest v1.0 and supporting rpms, taken from
sss-oscar tree. (Committed revision 4117.)

Needs to be tested in oscar trunk before closing this bug.

[Thomas Naughton]

Logged In: YES
user_id=288102

Since the fix for the latest APItest (to be
portable/standard) was to use the distro provided
'python-twisted' which is v1.3 based, the FutureWarnings may
occur on some systems.

They are simply warning so I'm not going to stress about
them. If needed I can apply the patch to Package.pm that
ignores these warning when running the apitest application
(python).