consistent virtualenv location?

[AlJohri]

hi, I was wondering if its possible to have a consistent named virtualenv path? Some people on my team like to use pycharm which I believe needs to have a consistent path to a virtualenv to work properly. It's not entirely clear to me right now when the virtualenv path (pipenv --venv) changes.

I understand I can use WORKON_HOME to change the folder but I believe the venv name is still subject to change?

[uranusjr]

The name is a combination of the project name and the hash of the full path of Pipfile, so it will stay the same as long as you don’t move the project.

https://github.com/kennethreitz/pipenv/blob/2628b5e3062314c3b5a7e09884cd036e1930437a/pipenv/project.py#L73-L95

I’m not sure if this can be relied on, or just implementation detail.

[kennethreitz]

We have no plans on changing this.

[kennethreitz]

It's best to run ($ pipenv --venv) to resolve the location of the virtualenv though, if you're going to access it programatically.

[kennethreitz]

Also there's a setting, via environment variable PIPENV_VENV_IN_PROJECT, which you can set, which will stick the virtualenv in project/.venv. That might be more appropriate for your team.

[AlJohri]

@kennethreitz it would be great if there was either a cli option or perhaps a project level settings file for pipenv. I would very much like my users to just have to run pipenv install and not have to modify anything in their global shell profile for a great first time user experience

[nateprewitt]

I'm still not opposed to a pipfile.conf setup similar to how pip.conf that would work in parallel with the environment variables. We've discussed this in the past though and the decision has leaned toward not implementing this as a feature.

[AlJohri]

Yeah, I would love to see something like pip.conf.

One thing that I don't particularly like is that PIPENV_SHELL_COMPAT is essentially required if you're using pyenv but it isn't explicitly documented (even though pyenv is mentioned other places in the docs). I feel like PIPENV_SHELL_COMPAT would be a great candidate to put in a pip.conf since pipenv shell pretty much doesn't work properly for pyenv users.

I'm just 100% focused on first time user experience for collaborators developing locally and I think pipenv solves a very large chunk of those problems for me, especially in combination with a tool like envdir. Just a few additional things like pip.conf would make that experience even better! 🎉

[kennethreitz]

not happening.

Pyenv is perfectly compatible with pipenv without -c — you just have to configure your shell properly. I opened a pull request to start that process already.

[kennethreitz]

e.g. pyenv is doing it wrong.

[AlJohri]

linking issue: pyenv/pyenv#982

[AlJohri]

@kennethreitz would you accept a PR that would allow for a custom virtualenv name? I tend to do multi-app projects so the path to my Pipfile would be myproject/api/Pipefile. I would ideally like the virtualenv to be called myproject-api. I end up with several virtualenv's all named something like api-somehashvalue right now

[kennethreitz]

no

[vlasovskikh]

@AlJohri Feel free to vote for PY-26492 to get pipenv support in PyCharm.