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
There's currently no way to specify interpreter command line arguments without also specifying the interpreter binary - both are done via "python". When used with VSCode, this means that there's no easy and obvious way to use the current selected interpreter in the IDE, but add some arguments to it - one needs to know about ${command:python.interpreterPath} (and I'm not sure this is even guaranteed to not get renamed or removed in future versions?).
We can enable this scenario by providing a separate property to specify just the arguments, similar to "args" for the debuggee itself, and "debugpyArgs" for injected debugpy; the obvious name would be "pythonArgs".
This should work in conjunction with existing semantics for "python" to maintain compatibility - if "python" is an array, and "pythonArgs" is also present, then we just concatenate them in that order to obtain the final value.
The text was updated successfully, but these errors were encountered:
…rguments
Expose "pythonArgs" to clients.
Make "python" usable in tests in lieu of "pythonPath", and make the runners use it.
Add tests for all combinations of "python"/"pythonPath" and "pythonArgs".
There's currently no way to specify interpreter command line arguments without also specifying the interpreter binary - both are done via "python". When used with VSCode, this means that there's no easy and obvious way to use the current selected interpreter in the IDE, but add some arguments to it - one needs to know about
${command:python.interpreterPath}
(and I'm not sure this is even guaranteed to not get renamed or removed in future versions?).We can enable this scenario by providing a separate property to specify just the arguments, similar to "args" for the debuggee itself, and "debugpyArgs" for injected debugpy; the obvious name would be "pythonArgs".
This should work in conjunction with existing semantics for "python" to maintain compatibility - if "python" is an array, and "pythonArgs" is also present, then we just concatenate them in that order to obtain the final value.
The text was updated successfully, but these errors were encountered: