![]() ![]() If anyone comes up with a "better" solution, just post it here and I'll change the answer to yours. I'm sure there might be a more elegant solution, but so far the aforementioned workaround came in handy. Now, pylint doesn't show this non-sense anymore, that's all I wanted :) Put simply, my custom modules get imported correctly when executing the scripts in VS Code, but the only annoying detail was that pylint didn't get it and showed me useless import-errors. pylintrc file, let alone all my attempts with no avail involving PYTHONPATH and environment-files etc. ![]() This solves my issue perfectly, as I honestly didn't find an easy solution to this problem via configuring e.g. Practically, I just had to add the comment # pylint: disable=import-error behind my custom imports like so: import _plotting_functions as aux_plot # pylint: disable=import-error It points towards the message control part of the pylint-docs. I found a great workaround for my problem with this answer. Visual Studio Code pylint: Unable to import 'protorpc' VS Code pylint(import-error) "Unable to import" subsub-module from custom directory
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |