Re: problems building strings

> 1. The docs talk about a Python strings implementation if the C code
> isn't compiled.  That doesn't seem to work for me.

And how did you come to that conclusion?  It works perfectly for
everyone else.  Also the Python version was the first version
written.  The C code is a human translation of the Python code
into C.

> C:\python.exe setup.py build_ext --compiler=mingw32

You don't build it that way.  Just use 

   python setup.py build --compiler=mingw32

Then copy the built pyd into the strings directory.

> 3. Does this require Microsoft's C compiler?
> (and an old version at that)

Nope.  I don't even have VC++.  Python 2.3 is built using
VC6 and hence you need a VC6 compatible compiler such as
MinGW.  Python 2.4 is built using VC7 and you need a compatible
compiler for 2.4 extensions.

> Maybe the binary of the needed files can be put in CVS or a separate
> distribution?

There is absolutely no need.  The only people who need the binary
version are the 2 of us who make the final distributables.  Everyone
else doesn't need to do anything.  The only drawback is that the
Python version is slower than the C version (it also uses more
memory).  And that is only going to be noticable when you are
importing thousands of entries with thousands of columns against
a similar sized existing information (this happens if you use
the test data generator for example).

Roger


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl