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

Latest update version 2020.8.101144 leads to broken input prompt in python debug console #367

Closed
IssamLaradji opened this issue Aug 14, 2020 · 4 comments

Comments

@IssamLaradji
Copy link

Latest update version 2020.8.101144 leads to broken input prompt in python debug console. This issue never happened in previous versions of VSCode or extension.

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur

  1. Create a simple python file containing this command
name = input('what is your name?')
print(name)
  1. Launch it with the python debugger. The debugger will just freeze at the prompt what is your name? and will not print user's input.

Actual behavior

The debugger will just freeze at the prompt what is your name? and will not print user's input.

Expected behavior

The debugger should just print the user's input and continue the program

Your Jupyter and/or Python environment

VSCode Version: 1.48
OS Version: macOS Catalina 10.15.6
Python Version: 3.7.6
Python extension: 2020.8.101144

Developer Tools Console Output

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

@karthiknadig karthiknadig transferred this issue from microsoft/vscode-python Aug 14, 2020
@fabioz
Copy link
Collaborator

fabioz commented Aug 17, 2020

One thing that changed is that the debugger no longer patches sys.stdin to give the CMD_INPUT_REQUESTED notification (i.e.: 499bbb2).

Does someone from the Jupyter notebook integration side know if this could be an issue? -- I wasn't aware of anyone needing that, but maybe it's needed in this case (if that's the case we need to make that an option instead of never patching it).

@karthiknadig
Copy link
Member

/cc @rchiodo

@karthiknadig
Copy link
Member

@IssamLaradji If you have a launch.json, try adding "redirectOutput": true to your launch.json debug configuration.

@fabioz
Copy link
Collaborator

fabioz commented Aug 21, 2020

Duplicate of; #370

@fabioz fabioz closed this as completed Aug 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants