Imports cannot be resolved in VSCode using Venv

[Splines]

Hey there, thanks for this really cool project ❤

I was just installing the latest bpy modules via pip install fake-bpy-module-4.3 inside a venv environment (Python 3.12.9, pip 24.2). Unfortunately, Pylance in VSCode reports Import "bpy" could not be resolved for my line import bpy.

What I've tried so far without success:

• I've uninstalled fake-bpy-module-latest and instead installed fake-bpy-module-4.3.
• I've restarted VSCode.
• I've restarted the Pylint server in VSCode.
• I've verified that my venv/lib/python3.12/site-packages/ folder inside my workspace contains the bpy folder. This is the case (also for other folders like bpy_extras etc.)

I understood the Install section in your Readme in the way that I can either install the stubs via PyPI, or manually download them and then tell VSCode where they are. So in my understanding, installing from PyPI, then restarting VSCode should be sufficient. Am I missing something?

By the way, I'm connected to WSL (Ubuntu 22.04 jammy), which usually doesn't pose any problems.

bpy-imports.mp4

[Splines]

Ok, just fixed it for me by adding this to my VSCode settings:

"python.analysis.extraPaths": [
    "venv/lib/python3.12/site-packages/"
],
"python.autoComplete.extraPaths": [
    "venv/lib/python3.12/site-packages/"
],

Might be worth to mention in the Readme that the subheadings in the installation procedure do not mean an either do this or do this, but rather:

• Either Install stubs via PyPI or download manually
• Then tell your editor about it in every case

[nutti]

@Splines

I think you don't need to change VSCode settings in this case.
Only you need to do is selecting the Python interpreter which points to venv environment.

[Splines]

Hey @nutti, that's what I did ;) See the video at 0:02. I had to add the extra path to my VSCode settings to tell Pylance to look into it, but it works like a charm now.