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.

Enable pylint suggestion keep showing up even though Pylint is enabled (in multiroot workspaces)

See original GitHub issue

Environment data

  • VS Code version: 1.54.0
  • Extension version (available under the Extensions sidebar): v2021.2.582707922
  • OS and version: Linux x64 5.11.2-arch1-1
  • Python version (& distribution if applicable, e.g. Anaconda): 3.5.10
  • Type of virtual environment used (N/A | venv | virtualenv | conda | …): venv
  • Relevant/affected Python packages and their versions:
  • Relevant/affected Python-related VS Code extensions and their versions: pylance-2021.3.0
  • Value of the python.languageServer setting: pylance-2021.3.0

Expected behaviour

After clicking “Enable pylint” button and have “python.linting.pylintEnabled” setting set to true, it is expected to stop seeing pop-up message “You have a pylintrc file in your workspace. Do you want to enable pylint?”.

Actual behaviour

The popup window “You have a pylintrc file in your workspace. Do you want to enable pylint?” pops up each time I start vscode despite on having python.linting.pylintEnabled" setting set to true.

Steps to reproduce:

  1. Open vscode
  2. Open any .py file
  3. See the pop up message “You have a pylintrc file in your workspace. Do you want to enable pylint?”.
  4. Click “Enable pylint button”.
  5. Close vscode
  6. Open vscode
  7. See that message again

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10

github_iconTop GitHub Comments

1reaction
karrtikrcommented, Mar 23, 2021

Great. FYI If you’re working with a workspace (.code-workspace), it’s considered a multiroot scenario. In this case you didn’t save the workspace yet, but you’re still adding folders to a workspace.

0reactions
kimadelinecommented, Sep 21, 2021

We removed the “You have a pylintrc file in your workspace. Do you want to enable pylint?” prompt as part of #17225, closing this issue as stale.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Linting Python in Visual Studio Code
Enabling a linter prompts you to install the required packages in your ... file in the workspace folder, as described on Pylint command...
Read more >
VS Code Python Intellisense and pylint not working properly
I have anaconda installed, but it doesn't make any difference which Python interpreter I use. Any suggestions? Thanks! Settings.json file: { " ...
Read more >
11 Best VS Code extensions for Python (2022)
This list contains the 10 best VS Code extensions for Python including Pylance, Sourcery, Python by Microsoft, and more.
Read more >
Pylance Now Default Language Server for Python in Visual ...
Pylance is now the default language server for Python in Visual Studio Code, providing IntelliSense functionality as of the May 2021 release ...
Read more >
VSCode 1.74.0 Download for Windows / Change Log ...
WSL docs use deprecated Chrome Debugger as extension example - Feature request: Show content of updates in RSS feed
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