Feature request: python virtualenvs

[stellarhoof]

When providing the full python executable I would expect sys.path to be set as:

$ .venv/bin/python -m pdb foo.py
$ (Pdb) import sys
$ (Pdb) sys.path
['', '/Users/berserk/Source/ocean/.venv/lib/python36.zip', '/Users/berserk/Source/ocean/.venv/lib/python3.6', '/Users/berserk/Source/ocean/.venv/lib/python3.6/lib-dynload', '/nix/store/mb1fwxr8w1n16fww8bp8spy6xy5dbjhm-python3-3.6.6-env/lib/python3.6', '/Users/berserk/Source/ocean/.venv/lib/python3.6/site-packages']

Whereas in :exe 'GdbStartPDB '.expand('%:p:h').'/.venv/bin/python -m pdb '.expand('%'), sys.path is equal to that of $ python -m pdb foo.py.

Might be the cause of #42, since my virtualenv's python is 3 and my system's python is 2.

[sakhnik]

That's strange. Technically, the python interpreter is spawned with execlp, which behaves similarly to the shell. If the full path is specified, that specific executable should be launched. And I can't reproduce your issue, sorry.

[stellarhoof]

To reproduce:

1. Make a new pipenv project with PIPENV_VENV_IN_PROJECT=1
2. Install a library not present in your system's python
3. Import it from a file and try to debug that

[sakhnik]

I've never worked with pipenv. Could you please give me a detailed list of specific commands just like for a dummy? For example:

• cd /tmp; mkdir proj && cd proj
• PIPENV_VENV_IN_PROJECT=1 pipenv <whatever>
• ...

[stellarhoof]

Pipenv integrates virtualenv and python dependency tracking. If you have a python project with a requirements.txt, pipenv will pick that up automatically on pipenv install. PIPENV_VENV_IN_PROJECT=1 makes it so that it will create the virutal environment folder in the project's directory. You just have to git clone any python repo and pipenv install inside. I hope this clarifies.

[sakhnik]

I'm afraid, I still can't reproduce the issue. I installed python 2.7.15 into ~/.pyenv and test/pyenv, and both work as expected. It must be something specific to your OS.
https://asciinema.org/a/218897

[gzbd]

Hi,

Sorry for commenting on a closed issue, but to use pipenv generated virtualenv in your project simply run the GDBStartPDB command like:
:GDBStartPDB pipenv run python -m pdb main.py

and your modules from virtualenv will be importable in debugging session :)