0

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
4

1 回答 1

0

1) 如果在 Canopy Preferences 中将 Canopy 设为默认 Python，那么 Gohlke 的二进制安装程序至少可以在没有任何手动注册表编辑的情况下工作。这个“默认”设置目前不是很健壮，所以如果你有其他 Python 的 PATH，它可能无法处理这个问题。

2）这可能不是一个完整的答案，但

HKEY_CURRENT_USER\Software\Python\PythonCore\2.7\InstallPath

应该设置为

"C:\Users\Tim\AppData\Local\Enthought\Canopy\User

3) 感谢您的报告。有这样一个错误，但它（我们认为！）在 1.1.0 中修复。如果您在此之前一直在进行更新，则修复可能尚未传播到用户环境。你愿意放弃你的用户 Python（以及你所有的包更新）来尝试干净地重新创建它吗？如果是这样，只需删除该用户目录。它将在下次启动时重新创建。

于 2013-11-02T02:02:27.660 回答