tb when using Python3 venv

[JohnSpeno]

Using python-mode within a python 3 virtualenv has an issue:

% vim
Error detected while processing /Users/speno/.vimrc:
line 224:
Traceback (most recent call last):
File "", line 8, in
IOError: [Errno 2] No such file or directory: '/Users/speno/Documents/venvs/
pika/bin/activate_this.py'

It's true. The virtualenvs created using python3's pyvenv command do not have a bin/activate_this.py file.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[nitipit]

Quick fix for now by copying activate_this.py from python2 virtualenv could help, I guess :9.

[sdlarsen]

Would indeed be nice with a fix.

[makmanalp]

+1 here. The thing is, when the virtualenv is activated and you run vim in it, you should already be in the virtualenv and so would one really need to run activate_this?

e.g. http://bugs.python.org/issue21496

[ypomortsev]

+1

[egoexpress]

+1
Creating 'Scripts' and touching 'Scripts/activate_this.py' is a workaround but it would be better if python-mode would properly support Python3 venv.

[relativistic]

This also seems to be a problem using python 2 if you use Enthought's canopy. Canopy uses a backport of venv:
https://support.enthought.com/entries/21802240-Use-venv-not-virtualenv-with-Canopy-Python

Using enthought's canopy, I get:

[Pymode]: error: [Errno 2] No such file or directory: '/Users/cpl29573/Library/Enthought/Canopy_64bit/User/Scripts/activate_
this.py'

[gilgamezh]

+1

[rusnasonov]

+1

[yoshiya0503]

+1

[toejough]

+1

[renodesper]

+1

[ghost]

please, fix it :)

[c4traz]

+1

[mvasilkov]

I second this issue very much.

[k3rry0n]

+1

[kuc2477]

+1

[tony]

+1

Or else python 3 is pretty much broken.

[searene]

+1

[tony]

#609 did the trick for me on Neovim, vim +python3 and also preserves python 2 completion.

[reven404]

I have also encountered this problem.
the main reason for this problem is the python3 venv module to use the absolute path in the virtual environment configuration.
check <virtual environment name>/bin/activate, found VIRTUAL_ENV, modify the correct path will be fix this problem. see below:

VIRTUAL_ENV = "/ Users /../../<virtual environment name>"
Export VIRTUAL_ENV¬

and then, reactive the virtual environment.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

Closed due to inactivity.