In the terminal, I still see the path on prompt in venv, and when I use deactivate, venv disappears but I cannot reproduce that in the warp.

Open
#1,358 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python, rust, shell
Domain
cli

Research direction

Start by reproducing the Poetry virtual-environment steps using source $(poetry env info --path)/bin/activate, then compare Warp with the default terminal before and after deactivate. Trace Warp's shell integration and prompt handling for the activation and deactivation entry points; done means the prompt shows the environment and directory consistently and removes both after deactivation.

Written by the indexing model from the issue text.

Description

area:shell-terminal bug needs-info ready-to-implement triaged
Discord username (optional)

BlueWater#1183

Describe the bug
I cannot figure out why warp works differently compared to terminal here. I am trying to use venv by sourcing because subshells do not support blocks. That is alright. But then, in terminal, I still see the path on prompt in venv, and when I use deactivate, venv disappears but I cannot reproduce that in warp.
To Reproduce
  1. Create a new folder in any directory using poetry new demo
  2. cd demo
  3. Set poetry to configure virtual env inside the project poetry config virtualenvs.in-project true
  4. Create a virtual environment in the folder poetry shell
  5. Exit out of this subshell because warp does not work in subshells using exit
  6. Source the virtual environment instead to remain in the same shell source $(poetry env info --path)/bin/activate
  7. Warp changes location to (.venv) and does not show the directory path any longer (default terminal app does)
  8. Use deactivate to deactivate the virtual environment. Default terminal app goes back to the directory path and no longer shows .venv. Warp still shows (.venv) and nothing changes.
Expected behaviour

No response

Screenshots

image

Operating System

No response

OS Version

Any

Shell Version

Any

Additional context
https://python-poetry.org/docs/basic-usage/#activating-the-virtual-environment
Warp Internal (ignore): linear-label:24888f54-df93-45d5-9bdd-e38f740cac19

No response

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.