Yeah, that's a reasonable idea... I've added a comment to the bug to take a
look at that too. Even if we expose the frame information via sys._getframe()
there will still be some missing information that's hard for us to produce, but
it might be able to unblock a number of useful scenarios.
Fr
In a related problem, could you guys take another look at sys._getframe when
implementing this feature? There is a lot going on in the returned frame
object from that function, but I think the big holdup for this is the stack
frame information. If the answer is still "no we aren't ready for th
Unfortunately there's no good way to do this. We have logic in PythonEngine to
filter stack frames but it's only exposed for doing this on exceptions, not on
arbitrary stack traces. And unfortunately v2.0 is in about the same shape -
all of its support revolves around exceptions too and it's f
This is all due to the wonderful issue created by COM components that can
be single-threaded or multi-threaded 'apartment'. I do not really fully
understand what this means (you can google about it and find lots of
information) - but I have run into it before and know how to fix it. The
winfo
Hi
Is there any way of accessing the python call stack in IronPython.
I'we tried using System.Diagnostics.StackTrace but most calls
on the clr call stack seem to be ironpython 'internals':
def Log(msg):
'''General logging function'''
print "%s: %s" % (StackTrace(1).GetFrame(0).GetMeth
Hi,
I'm trying to add the remote desktop activex control to a windows form and
am getting the following error. How can I fix this?
thanks for your help,
Krishna.
C:\IronPython-1.1>ipy -X:TabCompletion
IronPython 1.1 (1.1) on .NET 2.0.50727.312
Copyright (c) Microsoft Corporation. All rights rese
