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.

Pylint underlines the problem partially.

See original GitHub issue

Issue Type: Bug

The syntax erros are not underlined properly in this version. In the earlier versions this used to work fine.

The issue has also been raised on stackexchange: https://stackoverflow.com/questions/69947735/vscode-pylance-doesnt-identify-the-error-correctly-while-jedi-doesnt-mark-th

Extension version: 2021.11.1 VS Code version: Code 1.62.2 (3a6960b964327f0e3882ce18fcebd07ed191b316, 2021-11-11T20:56:38.428Z) OS version: Windows_NT x64 10.0.19042 Restricted Mode: No

System Info

Item	Value
CPUs	Intel® Core™ i3-5010U CPU @ 2.10GHz (4 x 2095)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	7.92GB (3.10GB free)
Process Argv	–crash-reporter-id c1b0ad07-809d-46b5-b3df-4f7dd5817d20
Screen Reader	no
VM	0%

A/B Experiments

vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263cf:30335440
vscoreces:30384385
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
vsccppwtct:30382698
bridge0708:30335490
dockerwalkthru:30377721
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30391933
pythonvspyt187:30373474
vsqsis200cf:30386380
vsaa593cf:30376535
vssld246cf:30386378

Issue Analytics

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

Top GitHub Comments

1reaction

debontecommented, Apr 21, 2022

Since the “partial underline” problem is an issue with pylint usage in VS Code, should it be transferred to vscode-python?

0reactions

karthiknadigcommented, Apr 21, 2022

Linting has change quite a bit since this bug was filed. We also have a new extension for pylint, currently in pre-release, please try it out: https://marketplace.visualstudio.com/items?itemName=ms-python.pylint