Re: How can i solve ImportError: No module named _vectorized when running unit test files?

NirmalaSudhir <[email protected]> writes:
> ...
> After including numpy and cython in  buildout.cfg eggs section i see these
> things during bin/buildout
>
> Warning: The C extension could not be compiled, speedups are not enabled.

Thus, you must find out why the "C extension could not be compiled".
If this C extension is "_vectorized" (which is quite likely), then this
will explain your later startup problems.


There are many possible reasons why the compilation of a C extension
fails (often some required header files or libraries are not installed
on your system). The most promising approach is to get more
information about the failure.

Starting "bin/buildout" with a lot of "-v" options
(e.g. "bin/buildout -v -v -v -v -v") will tell buildout to
produce a log of detailed information about the build process -
hopefully also (among a lot of irrelevant stuff)
why the above compilation failed. If this is not the case,
you may try to add some more "-v" options and see whether the output
changes.

Alternatively, you could try to "easy_install" "vectorized".
With a bit of luck, this will fail too to compile the C extension
and will give clues about the problem.


Alternatively, you could check the installation instructions
of the package (likely "vectorized"). If they are good, they
will tell you which headers/libraries/packages are required
for a successfull installation.



------------------------------------------------------------------------------