question-mark
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.

Prompted to enable pylint every time I launch VSCode

See original GitHub issue

Issue Type: Bug

Hello,

I have a python project with a .pylintrc file in the workspace. Everytime I launch VSCode - loading this project - I am prompted by one or more popups telling me “You have a pylintrc file in your workspace. Do you want to enable pylint?”

When I look in my settings, my user settings, workspace settings and project settings all have “Python > Linting: pylint Enabled” checked, so I really don’t know why I am seeing this popup every time.

Extension version: 2021.4.765268190 VS Code version: Code 1.55.2 (3c4e3df9e89829dce27b7b5c24508306b151f30d, 2021-04-13T09:35:57.887Z) OS version: Windows_NT x64 10.0.19042

System Info
Item Value
CPUs Intel® Core™ i7-5820K CPU @ 3.30GHz (12 x 3298)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 31.90GB (24.92GB free)
Process Argv –crash-reporter-id 99e05d5c-dfc7-4f2a-a69e-bc14f16577e3
Screen Reader no
VM 0%
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspyt653:30270858
pythonvspyt602:30294772
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vstry914:30276682
pythonvsnew554cf:30291488
pythontb:30283811
pythonvspyt551:30291414
vspre833cf:30267465
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
pythondataviewer:30285071
vscus158cf:30286554
vscgsv2:30294352

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:6

github_iconTop GitHub Comments

1reaction
kimadelinecommented, May 31, 2021

Hi @stevetwist, thank you for your patience!

Your issue is similar to what was reported in https://github.com/microsoft/vscode-python/issues/442, which is, as you can see, a long-standing issue.

I’m going to close this in favor of #442, feel free to upvote it to help us prioritize it.

Thank you!

0reactions
stevetwistcommented, May 13, 2021

Sorry for the delayed reply.

I can’t share the project itself, but I setup a test project to try and recreate the behavior.

I had a hard time at first recreating the same behavior (hence the delayed reply). I was eventually able to recreate the behavior, and I’m hoping the additional information I found will help you debug this.

First: I was only able to recreate this if the workspace folder is also a git repository. In a non-git workspace, this issue does not occur. However, simply performing ‘git init’ inside the workspace folder triggered the behaviour from that point on, when loading the workspace.

When I open the “broken” workspace in VSCode, and then open any file from that workspace in an editor, I see the linting popup. The first time I saw that popup and clicked “enable”, VSCode created a .vscode/settings.json in the workspace folder to enable linting (which you’ll see is included in the workspace I uploaded), yet this makes no difference, the popup still opens next time I open the workspace.

I did find a workaround that prevents the issue: hard-coding the settings in my workspace file to explicitly enable linting. This is not something the preferences will do (since those settings are enabled by default, I think), but by disabling them (so it wrote a setting) and then manually changing the setting from false to true, I was able to explicitly enable linting for my workspace. With that setting in place, I have not seen the popup since, and linting is working as expected. I have attached a “fixed” workspace, where I made those settings changes. I cannot get the popup to open for this workspace.

Thanks, Steve

brokenWorkspace.zip fixedWorkspace.zip

Read more comments on GitHub >

github_iconTop Results From Across the Web

Linting Python in Visual Studio Code
To enable linters, open the Command Palette (Ctrl+Shift+P) and select the Python: Select Linter command. The Select Linter command adds "python.linting.
Read more >
How do I enable Pylint in VSCode? - Stack Overflow
Launch VS Code. Open the Command Palette (⇧⌘P) and type shell command to find the Shell Command: Install 'code' command in PATH command....
Read more >
How to Set Default Python Interpreter in VS Code
On your VS code press Ctrl + Shift + P, to open the command palette. · Type and select “Python: Select Linter”. ·...
Read more >
Python in Visual Studio Code - October 2022 Release
Pylance has added an enhancement that allows users to include, exclude, and ignore paths via VS Code settings. Within each of these settings, ......
Read more >
“linter pylint is not installed” in VSCode - LinuxPip
You need to make sure pylint is installed in the same environment that VSCode detects. This may be the problem! Open up a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found