VSCode stubs/intellisense suddenly broken with TDI

Bugs
1

Hi everyone! All of a sudden I’ve noticed all my autocomplete/type checking with intellisense has suddenly broken in conjunction with Touchdesigner.

Things like:

op() is showing a type error as ‘Module is not callable’
according to op: Module(“.OPShortcut”) instead of OPShortcut like it used to

parent() ‘Module is not callable’
Inferred by vscode: parent: Module(“.ParentShortcut”)

Referring to just containerCOMP for example is inferred as Module(“containerCOMP”)

VScode seems to be interpreting everything as a Module rather than the class like its being imported in td.py

Is anyone else having this issue? It seems to occur in fresh projects for me as well and I cannot figure out why.

This is using the Touchdesigner bin/python.exe as the main interpreter path

Windows 10
Build 2025.32820
VSCode version 1.129.1

2

Jup, same here. @Ivan this seems to be related to vscode and not the TDI itself as I have this behavior not on the latest release.

3

I’ve encountered the same issue with both 2025.33070 and 2025.32820 TouchDesigner builds.

What fixed it for me is reverting VSCode Pylance extension to version 2026.2.1
(gear icon on the Pylance plugin > Install Specific Version…)

image
image382×546 18.5 KB

I’ve also uninstalled the vscode extension “Python Environments”, that was silently installed for me.

1 Like
4

Ah, thats a little more of an elegant way to go about it. I just created a local copy of Touchdesigner/…/binEtc/Lib//tdi and renamed every module so the classes and filenames (and also the imports) so it didn’t clash.

5

@HammersmithNeedlePum Can you describe specifically how you rearranged things to make them work?

I have low hopes of getting Pylance devs to address this problem!

6

I will have this going again for next release.