I've created a new test virtual environment in Enthought Canopy 1.1.1 (64-bit) using canopy_cli venv NEW_PATH
as per the documentation, however when I run a binary installer such as the latest numpy, it doesn't find the venv as a place where the package can be installed.
What is a minimal set of changes I need to make to the registry for my venv to be recognized by a binary like the latest numpy? It would be nice if in a future update this was done automatically, or via a switch.
Finally, I had to run canopy_cli venv
from the App environment, as when I run it from the default User environment I get the following error. Is this a bug?
C:\Users\Tim\AppData\Local\Enthought\Canopy\User\Scripts>canopy_cli venv
Traceback (most recent call last):
File "C:\Users\Tim\AppData\Local\Enthought\Canopy\User\Scripts\canopy_cli-scri
pt.py", line 7, in <module>
execfile(r"C:\Users\Tim\AppData\Local\Enthought\Canopy\App\Canopy-script.pyw
", ns)
File "C:\Users\Tim\AppData\Local\Enthought\Canopy\App\Canopy-script.pyw", line
757, in <module>
bootstrap()
File "C:\Users\Tim\AppData\Local\Enthought\Canopy\App\Canopy-script.pyw", line
335, in bootstrap
raise RuntimeError("no usable frozen versions were found")
RuntimeError: no usable frozen versions were found