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

Fix provided by 2018.9.1 doesn't work #2962

Closed
jsarneja opened this issue Oct 19, 2018 · 2 comments
Closed

Fix provided by 2018.9.1 doesn't work #2962

jsarneja opened this issue Oct 19, 2018 · 2 comments

Comments

@jsarneja
Copy link

Originally posted by @brettcannon in #2857 (comment)

Hi I installed the new extension 2018.9.1 but when running the for loop, it doesnt run in console unless I go to console and manually hit Enter. Any remedy here?

@jsarneja jsarneja changed the title FYI 2018.9.1 was just released with the fix for this! Fix provided by 2018.9.1 doesn't work Oct 19, 2018
@jsarneja
Copy link
Author

jsarneja commented Oct 19, 2018

Actual behavior

The problem cited in #2857 doesn't seem to get solved by installing the new Python extension (2018.9.1). When I run any for loop or any code snippet that required indentation, it just gets stuck in the console until I go to console manually and hit Enter

image

Expected behavior

The sample for loop should print 0,1,2,3,4 in console

Steps to reproduce:

Install the latest python extension 2018.9.1 and run the following code in VS code:

for a in range(5):
print(a)

Extension version: 2018.9.1
OS version: Windows 10 Enterprise x64

Logs

Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)


Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)



Reloading modules...
##########Linting Output - pylint##########

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

Uncaught TypeError: Cannot read property 'isWrapped' of undefined
    at Buffer.getWrappedRangeForLine (c:\Program Files\Microsoft VS Code\resources\app\node_modules.asar\vscode-xterm\lib\Buffer.js:205)
    at BufferStringIterator.next (c:\Program Files\Microsoft VS Code\resources\app\node_modules.asar\vscode-xterm\lib\Buffer.js:305)
    at Linkifier._linkifyRows (c:\Program Files\Microsoft VS Code\resources\app\node_modules.asar\vscode-xterm\lib\Linkifier.js:65)
    at c:\Program Files\Microsoft VS Code\resources\app\node_modules.asar\vscode-xterm\lib\Linkifier.js:53

@brettcannon
Copy link
Member

This is simply a limitation of how we are sending raw text down to the REPL, so the remedy in 2018.9.1 fixes what it was meant to do and doesn't add any new support around the preexisting limitation.

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

No branches or pull requests

2 participants