Re: Unittest Failure

Daniel Brodie <daniel@xxxxxxxxxxxxx> writes:

> I get the following when running a unit test before installation after 
> building
> (which seemed succsessful), on a Linux Fedora Core 2 (With some upgrades) and 
> a
> Python 2.3.
>
> This seems to be s 'simple' problem in terms of set_conversion_mode. Is it a
> fault on my part, or is it a bug? Is it serious or can I ignore it?
> (Please CC me since I am not registered)
>
> $  python setup.py test
> running test
> running build
> running build_py
> running build_ext
> === Testing in 'unittests' ===
> EE....
> ==========================================
> ERROR: unittests/test_callbacks.py
> ------------------------------------------
> Traceback (most recent call last):
>   File "run_remote_test.py", line 30, in ?
>     unittest.main(module=__import__(basename), testRunner=runner)
>   File "unittests/test_callbacks.py", line 2, in ?
>     from ctypes import *
>   File "/home/daniel/ctypes-0.9.1/ctypes/__init__.py", line 379, in ?
>     set_coversion_mode("ascii", "strict")
> NameError: name 'set_coversion_mode' is not defined

This mistake is long fixed in CVS, if at all possible please use the CVS
version - it contains lots of other fixes for unicode as well.
I just want to make the testsuite sucessfully run on OS X, after that
the next version will be released.

Thomas



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click