You know that the source code from IronPython is available, don't you? So
you're reflecting on the assemblies that IP generates? That's perhaps not a
fruitful use of your time, as they're planning on (major) changes to support
making callable-from-other-.Net-languages DLLs / libraries.
At 11:
I'm currently spiking out an "IronRuby". And I've been going to IronPython to see how y'all do things. It's been helpful, but there's not a lot of documentation and it's taking some time to figure things out (though reflector has been real helpful :) ).
I was wondering if anyone had an IM they'd
The fact that you can access this via exc_value.StackTrace is actually a bug -
and one that's already fixed internally for our next release. So for now
using the clsException field is the better way to go.
Another alternative here is that you can also explicitly catch a CLS exception.
Eg:
There's no file "excel.dll" -- what made you think there
was? The file that has the PIA for Excel is named
'Microsoft.Office.Interop.Excel.dll'. However, I have not attempted
to load it with IP (I don't have Office 2003 on the same machine as
IP).
You will probably want to use clr.AddReference
I
received a number of suggestions using 'regular' Python and using
PythonWin for Python2.4 and a number of
received examples and
code
snippets I got it working. Thank you.
Nevertheless, I also tried the suggestion on using
IronPython with
'just'
the PIAs. On a Microsoft WindowsXP pl
Works like a charm. Thanks!
Jacques
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Jonathan Jacobs
Verzonden: Thursday, February 09, 2006 1:19 PM
Aan: Discussion of IronPython
Onderwerp: Re: [IronPython] Exception.StackTrace gone?
J. de Hooge wrote:
> Do
Jonathan Jacobs wrote:
> You could either use sys.exc_value or .clsException.StackTrace on
> Exception objects. I don't know if the latter is a reliable source.
Or you could use traceback.py from the Python standard library.
--
Jonathan
___
users mail
J. de Hooge wrote:
> Does anyone know why it fails, and, more important, how I still can
> print a stack trace?
You could either use sys.exc_value or .clsException.StackTrace on
Exception objects. I don't know if the latter is a reliable source.
>>> import sys
>>> try:
... raise NotImplemen
Hi
In IP 0.95 I used to be able
to print the stacktrace of an exception as follows:
. . .
. . .
except Exception, exception:
.
. .
print
str (exception)
print
exception.StackTrace
.
. .
. . .
. . .
This fails in IP 1.0 Beta 2.
Does anyone know why i
