[ZODB-Dev] ZODB3 installation ambiguous conclusion

Laurence Rowe l at lrowe.co.uk
Sun Dec 20 15:50:06 EST 2009

2009/12/20 Ross Boylan <RossBoylan at stanfordalumni.org>:
> easy_install ZODB3 looked fairly good during installation until  the end:
> <quote>
> Processing transaction-1.0.0.tar.gz
> Running transaction-1.0.0\setup.py -q bdist_egg --dist-dir
> c:\users\ross\appdata\local\temp\easy_install-cw1i4f\transaction-1.0.0\egg-dist-tmp-z7nrfd
> Adding transaction 1.0.0 to easy-install.pth file
> Installed c:\python26\lib\site-packages\transaction-1.0.0-py2.6.egg
> Finished processing dependencies for ZODB3
> ********************************************************************************
>        An optional code optimization (C extension) could not be compiled.
>        Optimizations for this package will not be available!
> Unable to find vcvarsall.bat
> ********************************************************************************
> </quote>
> This seems to say things will work, just not as fast as they could.  But
> I'm a little puzzled why things would work at all, since I don't have a
> build environment on the machine (well, there is a compiler that's part
> of the MS SDK, but I'm not really sure how capable or operational it
> is--it did seem to compile some sample C code in the kit).
> Is there a pure python fallback for the C code?  I thought ZODB had some
> C-level magic.

ZODB requires C-code modules to work, but pre-compiled win32 eggs are
available, and presumably that is what easy_install picked. It's not
clear to me what generated that warning, but then I don't use Windows.


More information about the ZODB-Dev mailing list