microsoft / vscode-python

Python extension for Visual Studio Code
https://aka.ms/pvsc-marketplace
MIT License
4.25k stars 1.15k forks source link

`python.linting` error, but no such settings #23679

Open daegalus opened 2 weeks ago

daegalus commented 2 weeks ago

Type: Bug

Behaviour

Whenever I launch VS Code, it complains about python.linting entries in my settings, but I have no such entries in my settings. same with python.formatting. The only place they show up is in defaultSettings.json which I can not edit.

Expected Behaviour

No such error as I don't have said entries. (at least from what I see)

Extension version: 2024.8.1 VS Code version: Code 1.90.0 (89de5a8d4d6205e5b11647eb6a74844ca23d2573, 2024-06-04T19:43:07.605Z) OS version: Linux x64 6.8.11-300.fc40.x86_64 Modes:

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz (12 x 4445)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|1, 2, 2| |Memory (System)|30.97GB (15.32GB free)| |Process Argv|--crash-reporter-id 9fda2f6e-aac6-4ae8-847e-b98c771e6b00| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|gnome| |XDG_CURRENT_DESKTOP|GNOME| |XDG_SESSION_DESKTOP|gnome| |XDG_SESSION_TYPE|wayland|
A/B Experiments ``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 vscoreces:30445986 vscod805:30301674 binariesv615:30325510 vsaa593cf:30376535 py29gd2263:31024239 c4g48928:30535728 azure-dev_surveyone:30548225 2i9eh265:30646982 962ge761:30959799 pythongtdpath:30769146 welcomedialogc:30910334 pythonnoceb:30805159 asynctok:30898717 pythonregdiag2:30936856 pythonmypyd1:30879173 h48ei257:31000450 pythontbext0:30879054 accentitlementst:30995554 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 cppperfnew:31000557 dsvsc020:30976470 pythonait:31006305 jchc7451:31067544 chatpanelc:31048052 dsvsc021:30996838 jg8ic977:31013176 pythoncenvpt:31062603 a69g1124:31058053 dvdeprecation:31068756 dwnewjupytercf:31046870 legacy_priority:31077528 ```
daegalus commented 2 weeks ago

Screenshots, no workspace screenshot, as it is empty, and this happens on all workspaces:

Screenshot from 2024-06-24 14-07-13

Screenshot from 2024-06-24 14-06-57

Screenshot from 2024-06-24 14-05-00

Screenshot from 2024-06-24 14-04-54

Screenshot from 2024-06-24 14-04-15

karthiknadig commented 2 weeks ago

@daegalus If you open the settings UI ctrl+, it should show you various setting scopes. Sometimes there are 3 setting scopes User, machine and workspace. It could be in one of the machine scope settings.json files.

daegalus commented 2 weeks ago

@daegalus If you open the settings UI ctrl+, it should show you various setting scopes. Sometimes there are 3 setting scopes User, machine and workspace. It could be in one of the machine scope settings.json files.

Screenshot from 2024-06-24 16-25-13

There is no machine scope from what I am seeing.

karthiknadig commented 2 weeks ago

@daegalus In the workspace do you have a settings.json the above screenshot seems to be defaultSettings.json.

daegalus commented 2 weeks ago

@daegalus In the workspace do you have a settings.json the above screenshot seems to be defaultSettings.json.

As mentioned, I do not. It is empty, just {} when I access it. Just default settings and user settings.

This also happens across multiple workspaces, and we don't commit or add workspace settings files to our repos.

karthiknadig commented 2 weeks ago

I see. I will see if there is a way to add path to the settings file when it complains.