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

NirmalaSudhir <[email protected]> writes:
>    I already installed  cython and numpy.

Into the correct Python installation?

What do "bin/zopepy -c 'import numpy'" and
"bin/zopepy -c 'import Cython'" give you?

>And also I tried once again like
> you said, but still i get the same error. during bin/buildout 
> _vectorized.pyx is failed to load:(

The original error has been something like
"'numpy' or 'Cython' not installed; parts of 'vectorized' not build".
Do you now get the precise error as before - or is the error now
different?

If you now get a different error message (those error messages
(the more precise the better) are very important, as they are almost
the only thing we have to understand the problem), then
you have advanced one step.


If you still get the same error message ("numpy or Cython not installed ..."),
then your buildout environment still cannot use "numpy"
or "Cython" (the above "bin/zopepy" trials should check that).

Some people using "buildout" want their buildout environment as
self-contained as possible with those environments being able to
use only extensions installed by "buildout" itself (and not extensions
installed into the Python environment). Newer "buildout" versions
might support this (I have not yet met an installation
where my way to install packages (as described in a previous message)
failed to make the packages available to the "buildout" environment -
but I am not using the latest "buildout" versions).
You may want to add "numpy" and "Cython" to "eggs" definition
in your "buildout.cfg" -- before the "vectorized" entry and
then try "bin/buildout" again. Ideally, this would tell
"buildout" to install "numpy" and "Cython" into its environment.
If it succeeds, then the "buildout" environment should be able
to access those extensions.


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