|
Thanks Dino. I am debugging in Form.py in VS, just like a C# program. With your suggestions, I am able to step through the code, thanks.
Mitch http://softwareindustrialization.com
From: Dino Viehland
[mailto:[EMAIL PROTECTED]
On debugging: Are you debugging running the console, or did you put the code into a .py file and run it?
The reason I ask is when you’re running at the console we generate code in a mode that is essentially un-debuggable. The reason for this is that it’s the only way the code is collectible by the GC. But if you put the code into a .py file and import it, then you’ll get a much better experience – you should be able to step through the code at that point.
As for getting the IronPython source files – you might be able to solve this using Just My Code (Tools->Options->Debugging->General->Enable Just My Code). Another option is tweaking the exception handling settings (Ctrl-Alt-E) so thrown CLR exceptions don’t cause you to break in.
You could point VS at the IronPython source code, but then you’d be stepping through tons of IP source code to understand your exception. So hopefully the Just My Code option will do the right thing for you.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lesley & Mitch Barnett
Fixed my own error:
>>> from System.Reflection import * >>> a = Assembly.LoadFrom("mapack.dll") >>> Types = a.GetTypes() >>> for Type in Types: ... print Type ... Mapack.CholeskyDecomposition Mapack.EigenvalueDecomposition Mapack.LuDecomposition Mapack.Matrix Mapack.QrDecomposition Mapack.SingularValueDecomposition >>>
Still have the VS debugging issue…
snip |
_______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
