You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
# pyright: ignore[reportMissingModuleSource] on the same line - fixes it, but it might get noisy
# pyright: reportMissingModuleSource=none at the top of the file/project - might disable this warning for other imports where it can be useful
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.
or using some other hack, which might break at some point. So, the recommendation for users to use reportMissingModuleSource is probably our best option.
Activity
nutti commentedon Mar 31, 2026
@Andrej730
Agree.
But are we able to address this issue from fake-bpy-module side?
Andrej730 commentedon Apr 1, 2026
Probably not - only by
or using some other hack, which might break at some point. So, the recommendation for users to use
reportMissingModuleSourceis probably our best option.nutti commentedon Apr 1, 2026
@Andrej730
Then, shall we move to the discussion instead of issue?
I want to use issue session as a bug / feature request only.
Andrej730 commentedon Apr 1, 2026
@nutti sure, let's move it to discussions.