On Mon, 2 Apr 2007, Mike Taylor wrote:
I'm confused. If ctypes is needed, why aren't we compiling it? And what
does Cygwin's Python have to do with anything? (I specifically keep mine
at 2.3 in order to do setuptools testing, and AFAIK Cygwin's package
manager doesn't support having multiple installed Python versions.)
It seems kind of strange that we should be requiring people to install a
second version of Python in order to support a tool we added that requires
part of the stdlib that we don't build... I mean, why go out of our way to
patch Python *not* to build part of its standard library, just so we can
then make people have to install another whole copy of Python, separately?
(Note, by the way, that *not* building ctypes potentially breaks other
parts of the stdlib - the new Python "uuid" module uses it, for example.)
'ctypes' not being there on Windows is a bug.
I have no idea why, excluding it is not intentional.
I checked the VC project file and '_ctypes' is indeed being built and
importing it succeeds. Why importing 'ctypes' proper fails remains to be
determined.
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
