Hello!
I am dropping this mail to bring up an issue which cost me three good
evenings of time. Now that i figured it out i believe it is quite a
serious usability problem.
Gist of the problem: i have some C++ code wrapped with SWIG, so a native
extension. As with all software - there was a b
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 vi
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 13,
