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
Hi,
I just started working with Basilisk to build a hardware in-the-loop simulation. It is working correctly, but I'm having an issue with my code editor. As the imported modules are not Python code but compiled C/C++ with Swig, it seems that PyLance, the Python extension for VSCode, is unable to find them, even though it can access everything in the Python virtual environment.
This results in a copious amount of "Import could not be resolved" warnings and no integration with the editor's code completion.
I tried PyCharm with the same outcome.
Is there a workaround to make the Python LSP work with Basilisk's modules, or is the architecture fundamentally incompatible with that kind of functionality?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I just started working with Basilisk to build a hardware in-the-loop simulation. It is working correctly, but I'm having an issue with my code editor. As the imported modules are not Python code but compiled C/C++ with Swig, it seems that PyLance, the Python extension for VSCode, is unable to find them, even though it can access everything in the Python virtual environment.
This results in a copious amount of "Import could not be resolved" warnings and no integration with the editor's code completion.
I tried PyCharm with the same outcome.
Is there a workaround to make the Python LSP work with Basilisk's modules, or is the architecture fundamentally incompatible with that kind of functionality?
Beta Was this translation helpful? Give feedback.
All reactions