I'm guessing that yes, it is Reflection. I'm sure I could cobble together something that works, but I haven't wanted to spend the time to play with it that much. I'm pretty used to debugging by instrumenting code with a ton of logging and "print statements" regardless. From: Bradley Friedman [mailto:brad@fie.us] Sent: Monday, July 22, 2013 1:39 PM To: Tribble, Brett Cc: Jason Sachs; pythondotnet@python.org Subject: Re: [Python.NET] debugging I'm intrigued by this Brett. Is it that all the .NET Reflection gets in the way? I could certainly see that being a problem. Though I'd think you could get around it by setting break points at the entry points of concern? This is always a problem for these kinds of cross language bridges. Often each language consumes exceptions from the other and eliminates the "uncaught exception" as a useful debug tool. Though hard-core developers will often suggest that uncaught exceptions should never be allowed anyway. So maybe that's not really a problem. An example would be very interesting to see if nothing else. On Jul 22, 2013, at 3:32 PM, "Tribble, Brett" <btribble@ea.com<mailto:btribble@ea.com>> wrote: but trying to cross the bridge between the two leaves you debugging pythondotnet, and not the .NET project you actually want to debug.