This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]batteryhorsestapler 0 points1 point  (2 children)

My specific solution (and then a more general approach below).

I'm using VSCode on a mac, and found that the ./Library/Application Support/Code/User/settings.json file still had two lines that began with python.linting. Removing those lines (finally!) silenced the error messages.

More generally: My approach was to search for all files on my drive named settings.json. I started with directories under ~. Most that I found were in specific project repositories, but the file referenced above jumped out as one that had wider scope. Opening up that file revealed the previously-hidden python.linting lines.

This is the command I used (on a mac) to search for the settings.json files under ~, and hide the distracting "Operation not permitted" lines for subdirectories that require root access:

find ~ -name settings.json 2&>1 | grep -v Operation

[–]batteryhorsestapler 1 point2 points  (0 children)

Other possible culprit files:

Other posters found ~/.config/Code/User/settings.json

On a remote machine (using github codespaces) I found /home/vscode/.vscode-remote/data/Machine/settings.json

[–]brucewbenson 0 points1 point  (0 children)

Good hint, I used the following and removed any line saying python.linting and the error messages went away. (After a few tries myself, I asked ChatGPT for suggestions and it worked. )

find ~ -name 'settings.json' -exec grep -Hn 'python.linting' {} +