Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

unexpected token 'open'

See original GitHub issue

Issue Type: Bug

with open("test.html", 'w', encoding='utf-8') as f:
    f.write(page.text)

unexpected token ‘open’

Extension version: 2018.7.0 VS Code version: Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:43:53.668Z) OS version: Windows_NT x64 10.0.17134

System Info

Item	Value
CPUs	Intel® Core™ i5-5200U CPU @ 2.20GHz (4 x 2195)
GPU Status	2d_canvas: unavailable_software flash_3d: unavailable_software flash_stage3d: unavailable_software flash_stage3d_baseline: unavailable_software gpu_compositing: unavailable_software multiple_raster_threads: unavailable_off native_gpu_memory_buffers: disabled_software rasterization: unavailable_software video_decode: unavailable_software video_encode: unavailable_software vpx_decode: unavailable_software webgl: unavailable_off webgl2: unavailable_off
Memory (System)	7.92GB (4.18GB free)
Process Argv	D:\Microsoft VS Code\Code.exe F:\文档\GitHub\Protein
Screen Reader	no
VM	67%

Issue Analytics

State:
Created 5 years ago
Comments:11 (2 by maintainers)

Top GitHub Comments

1reaction

MikhailArkhipovcommented, Aug 21, 2018

Most probably was caused by threading issue where text buffer was going out of sync with between LS and VS Code. Fixed by https://github.com/Microsoft/PTVS/pull/4645

1reaction

JohnRomanskicommented, Aug 21, 2018

I am running Python 3.7.0

After deleting the languageServer directory, I loaded up the folder again. VSCode reported that it was downloading the Microsoft Python Language Server again.

After it re downloaded the new language server, I no longer have issues. I checked this with the two examples I discussed above as well as a blank Python file. Could it be that the language server just needed updating or something?

I did the same thing, and notice the server was downloaded again, and no longer received this error.