Re: [Ironpython-users] Memory Leak and Lightweight Scopes

Dino, Did you ever have a chance to look into this many moons ago, and if not, any tips on how to go about figuring it out? I'm pretty sure I am running into something similar. Thanks, Alex On Wed, Nov 16, 2011 at 10:54 AM, Dino Viehland wrote: > settrace() debugging should be perfectly fine

Re: [Ironpython-users] Enable Unmanaged Debugging IronPython

Adding DinoV because this sounds more like a PTVS issue than an IronPython issue - from the IronPython side there's nothing that should prevent it from working AFAIK. IronPython in VS uses the normal managed debugger. - Jeff On Wed, Jul 9, 2014 at 12:04 AM, John DiMatteo wrote: > Hello, > > Wh

[Ironpython-users] Enable Unmanaged Debugging IronPython

Hello, While debugging, with an IronPython startup project, I'm trying to step from IronPython to C# code to unmanaged C/C++ code. Is this possible? I am currently able to step from IronPython to C# when the startup project is IronPython. I'm also currently able to step from C# to unmanaged C/C

[Ironpython-users] IronPython, Daily Digest 7/8/2014

Hi ironpython, Here's your Daily Digest of new issues for project "IronPython". In today's digest:ISSUES 1. [New comment] print u'\xe4'.encode(sys.stdout.encoding) -> ? -- ISSUES 1. [New comment] print u'\xe4'.encode(sys.stdout.encoding) -> ? http:/