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
Python Adapter docs shows an example with isolated debugpy virtual environment in launch mode, separated from project venvs. I'd like to have similar separation for attach mode and tried:
cd~/myproject-A
~/.virtualenvs/debugpy/bin/python -m debugpy --listen localhost:7777 --wait-for-client main.py
# then use a config with `request = 'attach';`
This still had issues with not found pip dependencies installed in myproject-A, as we started main.py from the debugpy venv python interpreter.
So my current solution is to manually extend the known module path via PYTHONPATH:
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
-
Python Adapter docs shows an example with isolated
debugpy
virtual environment inlaunch
mode, separated from project venvs. I'd like to have similar separation forattach
mode and tried:This still had issues with not found pip dependencies installed in
myproject-A
, as we startedmain.py
from the debugpy venv python interpreter.So my current solution is to manually extend the known module path via
PYTHONPATH
:Is this the recommended setup for attach mode - or is there a simpler/better alternative which I haven't considered yet?
Beta Was this translation helpful? Give feedback.
All reactions