For the benefit of all you lucky non-Windows people out there, it is
very exceptional for a Windows PC to have a C compiler, so a Windows
installation should provide precompiled .pyd files or, as Graham
suggests, gracefully fail over to an all-Python substitute.

Unless using .py instead of .pyd entails truly horrific performance
penalties, I prefer an all-Python solution, which tends to be more
Billy-proof.

Jim Dukarm
DELTA-X RESEARCH

> Jim Dukarm wrote:

>> Now setup.py runs to completion. I have not figured out specifically
>> what was wrong, but possibly the setup is trying to copy a dll to a
>> nonexistent location, or something like that.

Graham Fawcett wrote:

> It was trying to *build* a DLL (or rather a .pyd file, really the same
> thing). My guess is you don't have a C compiler on the workstation...
> definitely a common state of affairs on Windows machines. (Or, a
> configuration problem is preventing Python's distutils from running your
> compiler.)