I will up front that coming from a "Strict Language" background and doing a lot of Java recently that Python without linters feels like Motorcycle Riding Without a Helmet, I have an intense interest in them, to make sure I am learning correctly and later to help make sure my production code is safe for public consumption...I am a static analysis addict in general when it comes to production code and have watched them (static analyzers) go from classical Lint to things 5000 times better in my lifetime.
So I had set up VSCode because it seems to be available everywhere I need to work, it is free, and also seems to have a LOT of active users and supporters.
Everything was tickety-boo until I got to the part where I started making my own modules and importing them into sources that called them.
They work fine at runtime, but PyLint doesn't seem to see that the import is valid even tho the importer and the imported module are sitting right in the same directory.
I get spurious messages like:
"unresolved import 'indef_art'"
I am using PyLint as the primary linter which seems to have been the default until very recently, when VSCode started pitching PyLance towards me.
I saw a few suggestions online that all required knowing more about configuring PyLint and configuring VSCode for Python linting than I currently grok.
If respondents feel PyLint is no longer a good choice I will switch to PyLance or something else that VSCode supports and this particular question might be moot...
As a side note, my wife finds it humorous that the class of checkers is called linters because it reminds her of the things that catch the fluff and hair and junk in the dryer during laundry, I told her I am 99% sure that is what they are named after.
I don't like that guy. The tiny ad agrees with me.