`reportMissingModuleSource` on `import bpy`

[Andrej730]

It seems as a consequence of #433, now a warning pops up in VS Code ("Import "bpy" could not be resolved from source Pylance[reportMissingModuleSource]"):

What do you think is the best workaround to avoid it?

Options that came to mind:

1. # pyright: ignore[reportMissingModuleSource] on the same line - fixes it, but it might get noisy
2. # pyright: reportMissingModuleSource=none at the top of the file/project - might disable this warning for other imports where it can be useful
3. installing some older version of fake-bpy-module in parallel that doesn't have -stubs, but then it defies the puprose of Follow "Distributing type information" by renaming modules to *-stubs (such as bpy-stubs) #433

Thinking about it more, I can't find any scenario where reportMissingModuleSource might actually help in case of a Blender addon, since all the imports will be inside Blender's context either way, so their concrete sources shouldn't be discoverable inside VS Code project. So reportMissingModuleSource should become a new disabled setting in all Blender related projects, along the reportInvalidTypeForm we disable due to Blender API quirks.

Does it makes sense, any caveats to this?

[nutti]

@Andrej730
Agree.
But are we able to address this issue from fake-bpy-module side?

[Andrej730]

Probably not - only by

3. installing some older version of fake-bpy-module in parallel that doesn't have -stubs, but then it defies the puprose of Follow "Distributing type information" by renaming modules to *-stubs (such as bpy-stubs) #433

or using some other hack, which might break at some point. So, the recommendation for users to use reportMissingModuleSource is probably our best option.

[nutti]

@Andrej730
Then, shall we move to the discussion instead of issue?
I want to use issue session as a bug / feature request only.

[Andrej730]

@nutti sure, let's move it to discussions.