Running pylint within Visual Studio 2017 doesn't work - python-3.x

Question

I have pylint installed in my virtual environment, and the virtual environment is configured and activated in the solution.
When I run pylint through command prompt (after activating the virtual environment), it works:
C:\Users\AmosH\Documents\Workspace\local_gallery>pylint projects
Using config file C:\Users\AmosH\Documents\Workspace\local_gallery\.pylintrc
************* Module projects.admin
C: 1, 0: Missing module docstring (missing-docstring)
************* Module projects.apps
C: 1, 0: Missing module docstring (missing-docstring)
C: 4, 0: Missing class docstring (missing-docstring)
************* Module projects.models
C: 1, 0: Missing module docstring (missing-docstring)
C: 5, 0: Missing class docstring (missing-docstring)
C: 15, 4: Missing method docstring (missing-docstring)
...
-----------------------------------
Your code has been rated at 2.29/10
But when I run it within Visual Studio (Right click on project > Python > Run PyLint) it simply shows strange warnings:
Severity Code Description Project File Line Suppression State
Warning No module named general\admin.py [F:fatal] local_gallery general\admin.py 1
Warning No module named download_some_images.py [F:fatal] local_gallery download_some_images.py 1
Warning No module named general\apps.py [F:fatal] local_gallery general\apps.py 1
Warning No module named general\management\commands\populate_db.py [F:fatal] local_gallery general\management\commands\populate_db.py 1
Warning No module named general\management\commands\__init__.py [F:fatal] local_gallery general\management\commands\__init__.py 1
Warning No module named general\management\__init__.py [F:fatal] local_gallery general\management\__init__.py 1
Warning No module named general\migrations\__init__.py [F:fatal] local_gallery general\migrations\__init__.py 1
Warning No module named general\models.py [F:fatal] local_gallery general\models.py 1
Warning No module named general\templatetags\lg.py [F:fatal] local_gallery general\templatetags\lg.py 1
Warning No module named general\tests.py [F:fatal] local_gallery general\tests.py 1
Warning No module named general\views.py [F:fatal] local_gallery general\views.py 1
Warning No module named general\__init__.py [F:fatal] local_gallery general\__init__.py 1
Warning No module named local_gallery\renderers.py [F:fatal] local_gallery local_gallery\renderers.py 1
Warning No module named local_gallery\settings.py [F:fatal] local_gallery local_gallery\settings.py 1
Warning No module named local_gallery\urls.py [F:fatal] local_gallery local_gallery\urls.py 1
...
Each file cannot load itself, or something like this (note that each module doesn't try to load other modules, but itself, and fails).
When I double click on any of the warnings, I might get an error like this:
Or another one that refers me to "C:\Users\AmosH\AppData\Roaming\Microsoft\VisualStudio\15.0_e34de02d\ActivityLog.xml", in which I'll find something like this:
System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\AmosH\Documents\Workspace\general\management\__init__.py'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) at Microsoft.VisualStudio.Text.Implementation.TextDocumentFactoryService.OpenFileGuts(String filePath, DateTime& lastModifiedTimeUtc, Int64& fileSize) at Microsoft.VisualStudio.Text.Implementation.TextDocumentFactoryService.OpenFile(String filePath, DateTime& lastModifiedTimeUtc, Int64& fileSize) at Microsoft.VisualStudio.Text.Implementation.TextDocumentFactoryService.CreateAndLoadTextDocument(String filePath, IContentType contentType, Boolean attemptUtf8Detection, Boolean& characterSubstitutionsOccurred) at Microsoft.VisualStudio.Editor.Implementation.TextDocData.InitializeNewTextBufferFromFile(String fileName, Object source) at Microsoft.VisualStudio.Editor.Implementation.TextDocData.Load(String pszFilename, UInt32 grfMode, Int32 fReadOnly, Object source) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.VisualStudio.ErrorHandler.ThrowOnFailure(Int32 hr, Int32[] expectedHRFailure) at Microsoft.VisualStudio.Shell.VsShellUtilities.OpenDocument(IServiceProvider provider, String fullPath, Guid logicalView, IVsUIHierarchy& hierarchy, UInt32& itemID, IVsWindowFrame& windowFrame, IVsTextView& view) at Microsoft.VisualStudioTools.Project.VsUtilities.OpenDocument(IServiceProvider serviceProvider, String filename, IVsTextView& viewAdapter, IVsWindowFrame& pWindowFrame) at Microsoft.VisualStudioTools.Project.VsUtilities.NavigateTo(IServiceProvider serviceProvider, String filename, Guid docViewGuidType, Int32 line, Int32 col) at Microsoft.PythonTools.Project.CustomCommand.ErrorListRedirector.OnNavigate(Object sender, EventArgs e) at Microsoft.VisualStudio.Shell.Task.OnNavigate(EventArgs e) at Microsoft.VisualStudio.Shell.Task.Microsoft.VisualStudio.Shell.Interop.IVsTaskItem.NavigateTo() at Microsoft.VisualStudio.ErrorListPkg.Shims.ErrorListPackageEventProcessor.PreprocessNavigate(ITableEntryHandle entryHandle, TableEntryNavigateEventArgs e) at Microsoft.VisualStudio.Shell.TableControl.Implementation.TableControlEventManager.<>c__DisplayClass40_0.<OnEntryElementNavigate>b__2(ITableControlEventProcessor p, ITableEntryHandle entry) at Microsoft.VisualStudio.Shell.TableControl.Implementation.TableControlEventManager.<>c__DisplayClass60_1`1.<EventProcessorHandler>b__0() at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.CallExtensionPoint(Object errorSource, Action call) --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)

Answer 1

Apparently there is a bug in Visual Studio 2017 that causes this issue if you do not choose the location of the .pyproj file as the root directory of your project. In my case I chose the parent directory, and Visual Studio 2017 did not make the proper adjustments required for pylint to work under these circumstances. Whenever I run pylint through Visual Studio 2017 it seeks the modules in the parent directory, even though I can navigate through my project and edit the files with no problems at all using Visual Studio 2017. It is strange indeed.