It would make sense to configure it in the same way as we do in src/tox.ini (see section testenv:pycodestyle-minimal). https://github.com/sagemath/sage/blob/develop/src/tox.ini#L92
If you want to work on this, could you open at ticket please? On Wednesday, August 24, 2022 at 1:41:40 PM UTC-7 davida...@gmail.com wrote: > Hello everybody, > > Recently, the pycodestyle linter as been enabled by default in the vscode > setting file (I think in the ticket #33739 > <https://trac.sagemath.org/ticket/33739>). While I'm not opposed to this > as it helps me following good coding conventions, many python files are now > blood red of warnings, which I find a bit distracting. Here's an example > among many others: > > [image: vscode.jpg] > > Many of those errors are E3 or E5 type. Of course I could deactivate the > linter but this would change the file .vscode/setting.json which is > included in the git repo so it's not ideal. > > I was wondering if there was a solution to this (maybe by tuning down the > linter or simply ignore the setting file)? > > David A. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/44f494f9-18f2-4353-bfc4-c721ef65d40cn%40googlegroups.com.
