Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using up-arrow in Python terminal for conda env does not show last command #1690

Closed
jn7dt opened this issue May 15, 2018 · 2 comments · May be fixed by bumplzz69/vscode-python#30 or irinazheltisheva/vscode-python#12

Comments

@jn7dt
Copy link

jn7dt commented May 15, 2018

Environment data

  • VS Code version: 1.23.1
  • Extension version (available under the Extensions sidebar): 2018.4.0
  • OS and version: Windows 10 1709 (Build 16299.309)
  • Python version (& distribution if applicable, e.g. Anaconda): 3.6.4 Anaconda (64-bit)
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
  • Relevant/affected Python packages and their versions:

Actual behavior

  • last command is not displayed in integrated terminal when up-arrow is pressed within Python REPL

Expected behavior

  • last command would be displayed

Steps to reproduce:

  1. Ctrl + Shift + P -> Python: Create Terminal create_python_terminal
  2. (in terminal window) type "python" to start REPL terminal_start_activate_env
  3. (enter any command, for example:) test = 'testing' up_arrow_nothing
  4. press up-arrow to display last command (nothing happens)

Starting REPL with Ctrl + Shift + P -> Python: Start REPL and then continuing with steps 3 and 4 results in the same issue.

@brettcannon
Copy link
Member

We have no direct control over the terminal, so if this isnt' working then it has to do with your Python installation -- verify by trying this in an external terminal -- or with VS Code itself and how Anaconda's build of Python interact with each other.

@jn7dt
Copy link
Author

jn7dt commented May 16, 2018

Thanks Brett! I'll post to VS Code then - external terminal works as expected.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants