[IronPython] IronPython 2.6 Bugs

Dino Viehland dinov at microsoft.com
Tue Aug 18 17:42:20 CEST 2009

That's convenient because I've been working on fixing that one along
w/ another related bug for getting PyDev debugging to work.

This one will require that you provide a -X:Tracing command line flag
so that we always have the tracing code gen.  But it works on my machine
as of a couple of days ago (there's just other things which are still

So expect this to be in 2.6RC1.

> -----Original Message-----
> From: users-bounces at lists.ironpython.com [mailto:users-
> bounces at lists.ironpython.com] On Behalf Of Michael Foord
> Sent: Tuesday, August 18, 2009 3:31 AM
> To: Discussion of IronPython
> Subject: [IronPython] IronPython 2.6 Bugs
> Hello Dino,
> Sorry - I lost the original email so am sending a fresh one. :-)
> You asked what bugs in particular we would like to see fixed in 2.6
> final. I am *very* keen to see pdb work with IronPython 2.6, and in
> particular set_trace and post_mortem which don't work in Beta 2. There
> is an open codeplex issue for this somewhere...
> Michael
> --
> http://www.ironpythoninaction.com/
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

More information about the Ironpython-users mailing list