Re: [Adonthell-devel] Gentlemen, start your Windows!

[Alexandre Courbot]

Maybe the ending! :)

Actually, this is probably *once again* a stupid problem.

Google revealed this page: http://www.python.org/2.2/bugs.html where you
see under the "Incompatibilities between Python 2.1[.1] and Python 2.2"
section:

# type("").__name__ == "str" # was "string"

The type name of the strings seems to have changed between 2.1 and 2.2.
Effectively:

$ python2.1
Python 2.1.1 (#1, Nov 11 2001, 18:19:24) 
[GCC 2.95.4 20011006 (Debian prerelease)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> type("")
<type 'string'>

and

$ python2.2
Python 2.2.1c1 (#1, Mar 15 2002, 08:13:47) 
[GCC 2.95.4 20011002 (Debian prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> type("")
<type 'str'>

So far I've compiled using 2.2.1 under Linux and 2.2.2 under WineX.
What's the problem anyway? PyString_Check should work despite of this,
as it's not SWIG that is checking the type name directly. This is where
it starts becoming stupid. See, I've got the .a import library from a
guy on the Python list, and the DLL somewhere on the web. So it might
well be, that I *ahem* were compiling on 2.1 and using 2.2's DLL, or
vice versa... 

Recompiling for Linux with 2.1 and 2.2 confirms this. str for 2.2,
string for 2.1, but both works if linked properly.

Does someone has a *consistent* mingw32 Python system installed, and
could send me the .h, .a and .dll files? (2.1 and 2.2 version accepted
^_^)

Alex.
-- 
http://www.gnurou.org