停用virtualenvwapper和anaconda中的冲突 [英] deactivate conflict in virtualenvwapper and anaconda

查看:110
本文介绍了停用virtualenvwapper和anaconda中的冲突的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用virtualenv切换我的python dev env.但是当我运行workon my_env时,遇到了这样的错误消息:

I'm using virtualenv to switch my python dev env. But when I run workon my_env, I meet such error message:

Error: deactivate must be sourced. Run 'source deactivate'
instead of 'deactivate'.

Usage: source deactivate

removes the 'bin' directory of the environment activated with 'source
activate' from PATH.

在Google上进行一些搜索后,似乎在/usr/local/bin/virtualenvwrapper.sh中定义的workon调用了deactivate.在Anaconda的垃圾箱中有一个同名的脚本,因此它被workon错误地调用.

After some searches on google, it seems that workon, which is defined in /usr/local/bin/virtualenvwrapper.sh, calls deactivate. And there is a script with the same name is present in Anaconda's bin, so it gets called by workon by mistake.

是否有解决此冲突的建议?

Any suggestion for working around this conflict?

推荐答案

对我有用的一种解决方案是在Anaconda的垃圾箱中重命名deactivate:

One solution which works for me is to rename deactivate in Anaconda's bin:

mv deactivate conda-deactivate

这篇关于停用virtualenvwapper和anaconda中的冲突的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆