On 3/13/23, Rokas Kupstys wrote:
> I eventually stumbled on to process list showing
> ".venv/Scripts/python.exe" having spawned a subprocess... Which led me
> to "PC/launcher.c" which is what ".venv/Scripts/python.exe" really is.
For a standard Python installation, you can create a virtual
On 3/14/2023 7:13 AM, Rokas Kupstys wrote:
> Still, i think there can be an improvement in this area, and it would
> likely be quite cheap. The biggest problem is people being unaware what
> is going on. IsDebuggerPresent()/CheckRemoteDebuggerPresent() could be
> used for checking debugger
As Steve suggested i think most friction-less path is to run python
interpreter directly while specifying site-packages of virtualenv in
PYTHONPATH. I already specify additional paths there anyway, since
extensions are built with cmake and i wanted to achieve fast iteration
times, being able
Is it easier to simply run python outside a virtualenv? They are great, but
maybe when debugging an extension module, it's not so hard to just not use
it :-)
You also might want to give conda environments a try -- they include
Python, so probably won't have the same issue.
-CHB
On Mon, Mar
Hi Rokas
The typical solution (which I myself use frequently) is to enable your
debugger to attach to child processes automatically. It can make things
a bit noisier, but it's generally manageable, especially if you've got
breakpoints set in your own code.
Another option is to not use the
