Does not enter pipenv shell when creating new terminal directly in a pipenv folder

[danielcompton]

If I create a new terminal tab, it inherits the previous tabs location. If I do this in a pipenv folder, the original terminal gets the pipenv shell applied (from cding into it), but the new tab opened directly in that folder doesn't.

[ParthS007]

Closing due to inactivity 👍

[lig]

@ParthS007 I don't understand why this one is closed

[lig]

Affects me as well. Opening a new terminal directly in a folder which has Pipfile doesn't activate the pipenv shell. Typing cd . after that activates pipenv shell as expected.

It is expected to have pipenv shell to be activated when fish has been started directly in a folder containg Pipfile.

[rahul286]

Update

I had to roll back the change as it was messing up the PATH order as below (brew python was accessible before pipenv python in pipenv shell)

❯ which -a python
/opt/homebrew/opt/python/libexec/bin/python
/Users/rahul286/.local/share/virtualenvs/random-eAAq4JbF/bin/python

---

I also came here looking for a solution to this issue.

As of now I got desired behavior by editing the line

fish-pipenv/conf.d/pipenv.fish

Line 5 in 7c0fa5c

function __pipenv_shell_activate --on-variable PWD

with

function __pipenv_shell_activate --on-variable PWD --on-event fish_prompt

I believe we need to fire function __pipenv_shell_activate on some event related to a new terminal tab creation. fish_prompt does the job but it runs __pipenv_shell_activate function every time you're run any command. So it is not efficient.

[franciscolourenco]

You could probably also solve this problem by calling __pipenv_shell_activate from config.fish