Update .env

[Timoms]

Added visual indicator that pipenv is active as mentioned in #97

[coveralls]

Pull Request Test Coverage Report for Build 1867217758

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 92.084%

---

Totals
Change from base Build 1865042100:	0.0%
Covered Lines:	3920
Relevant Lines:	4257

---

💛 - Coveralls

[yschroeder]

This does not work for me. If I do pipenv shell my prompt looks like before. I am using zsh with GRML config which already heavily mods my prompt.

It works in a plain bash though.

So I guess LGTM.

[Timoms]

So it doesn't mess up your current config but improves the "normal" bash one, right?
Don't want this PR to mess with other configs but improve default ones.

I am a WSL2/Ubuntu user with some minimal mods to the bashrc - and it makes quite the difference.

[tribut]

This looks harmless enough, but is feels like this belongs to pipenv, not every project using it.

Indeed, pipenv includes code that should be doing exactly the same thing: https://github.com/pypa/pipenv/blob/main/pipenv/shells.py#L91-L94

Just found this upstream issue - apparently it's a pipenv/powershell bug? pypa/pipenv#3505

[Timoms]

This looks harmless enough, but is feels like this belongs to pipenv, not every project using it.

Indeed, pipenv includes code that should be doing exactly the same thing: https://github.com/pypa/pipenv/blob/main/pipenv/shells.py#L91-L94

Just found this upstream issue - apparently it's a pipenv/powershell bug? pypa/pipenv#3505

Seems like the issue is around since 2018 and got only fixed for cmd recently.
I am not sure if pipenv fixes this in the near future (since the mentioned issue is around like 2 years now).

[tribut]

If your change doesn't duplicate the prompt for systems where it currently works (if any), sure. We can remove it later once it works.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.