Python Up Arrow not working on gitbash intergrated terminal w venv running

[chrisdel101]

Py up arrow history not working in shell while venv is running. Venv is essential to py dev so this is huge pain. Need instead to use external terminal which is bothersome.

See post that I've commented in 2 years ago as documented history.

Does this issue occur when all extensions are disabled?: Yes/No

Yes - all extensions are disabled + reloaded, but venv is running. Using pipenv for virtual environment.

• VS Code Version: 1.95.3
• OS Version: Win 11
• Python 3.12.6
• pipenv, version 2024.4.0

Steps to Reproduce:

1. Open shell and run python command
2. Try up arrow and fail

If this is a setting issue, or some kind of user error, I'd be happy to hear how to fix this :)

[anthonykim1]

Thanks for filing this issue.
Does this issue persist when you use different shell other than git bash?
Please note git bash is not currently officially supported from Python extension.

[chrisdel101]

Yeah it works if I try powershell but I need a linux shell. Are there any Microsoft does support?
I tried this before with all extensions disabled, but I must not have restarted the shell b/c I retried with new shell, and all disabled, and the up arrow works. So it is extension after all.
Still very disruptive. Thanks for the reply.

[github-actions]

Hey @anthonykim1, this issue might need further attention.

@chrisdel101, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[chrisdel101]

Closing but hoping to leave commenting open in case others come here later.

[anthonykim1]

Apologies for late response here @chrisdel101

Currently gitbash is not officially supported by Python extension.

Have you tried zsh, bash?

but I must not have restarted the shell b/c I retried with new shell,

I assume its gitbash when you say "new shell"

If it is the case that gitbash is messing with your arrow keys only when Python extension is enabled, I think it will be worth having this open.

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!