Closed LightArrowsEXE closed 1 year ago
Imo vsrepo shouldn't even handle any output path and the sort, just blindly open subprocess of vsgenstubs4 and that's it Doesn't even make sense to have one in roaming site-packages and another in the actual install
This is fixed upstream now.
This still seems to persist when using vsrepo install plugin
. I can fix it manually by deleting the vapoursynth-stubs/__init__.pyi
file and running vsgenstubs4
after, but that's rather annoying.
When generating or updating the VS stubs, the following exception occurs...
...except it stores this inside the
__init__.pyi
fileThis means stubs never load, however running
vsgenstubs4
myself from the terminal seems to properly stick them in the localsite-packages
. However, the roaming one gets prioritised, meaning stubs never get loaded. plsfix.