Re: [Pypgsql-users] Unit test script appears to have problems

[Gerhard <ger...@gm...>]

* Steve Waterbury <ste...@gs...> [2002-05-20 16:41 -0400]:
> Gerhard Häring wrote:
> > 
> > * Steve Waterbury <ste...@gs...> [2002-05-20 09:37 -0400]:
> > > I installed PyPgSQL and ran PgSQLTestCases.py, which gave 29 errors -- but
> > > these seem to be problems with the test scripts rather than with
> > > PyPgSQL itself.  All errors came down to 4 methods missing in various unit
> > > test scripts:  "assertEqual", "assertEquals" [sic -- typo?],
> > > "failUnlessRaises", and "fail".
> > 
> > Strange. Which version of Python is this? If it is 2.1 or later, do you
> > use the included unittest module or did you perhaps overwrite it with an
> > updated or outdated version?
> 
> I'm using Python 2.2.1 (#1, Apr 18 2002, 01:54:11)

Ok. That's fine, reinstalling the original unittest.py and making sure
it is really used should already do the trick.

> and PyUnit 1.4.1, which I installed "over" the included one when I saw that 
> the tests were failing.

That isn't necessary. The pyunit in 2.2.1 seems to be _more_ up-to-date
than what can be found on the pyunit site. But every pyunit >= 1.4.0
should be ok from what I see.

> (They failed the same way with the PyUnit that was included in Python
> 2.2.1.) 

Really strange. Let's try to find out what happened:

You can start Python with "python -v" and then "import unittest". This
should show which unittest.py is really loaded. It should look about
like:

>>> import unittest
# /usr/local/lib/python2.2/unittest.pyc matches
# /usr/local/lib/python2.2/unittest.py
[...]

Then you can use "print unittest.__version__" to see the revision number
of the module.

Gerhard
-- 
mail:   gerhard <at> bigfoot <dot> de       registered Linux user #64239
web:    http://www.cs.fhm.edu/~ifw00065/    OpenPGP public key id AD24C930
public key fingerprint: 3FCC 8700 3012 0A9E B0C9  3667 814B 9CAA AD24 C930
reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))