Major Description
A codebase I'm familiar with has requirements.txt files all over the place. In order to get proper pylint support, this means either making sure the modules are in the environment some how, such as building a container. But theoretically, pylint.py could install them into a scratch directory (e.g., pip install --user or via venv or whatever) and then run pylint against the source with that in the path. This seems especially do-able in a docker container.