Unfortunately, now you will be 'punished' for releasing pyc.py. The
following code does some funny things when compiled:
print "1"
import clr
print "2"
import os
print "3"
print os.getcwd()
import sys
print "4"
print sys.version
This works fine if you launch it as a script with IP2. You get:
Does anyone know where this updated sample referred to in the announcement
can be found? Thanks,
David
___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
This looks interesting. However I blew up the program the moment I tried
it. I think the problem is that you use a relative path to open your
syntax files but when you go to File Open the source file, the current
directory gets changed to where ever, and then the program blows up at
line 24 o
Hi, just a user here - but I tried this to see if I could reproduce it and
could not- sorry.
My environment: Python 2.4.4 and Python 2.5.1, Windows XP SP2, Visual
Studio Beta 2, the released version of .net 3.5 and IP 2A6. In the VS
command line with either version of python I do not get a cra
> Yes, Parser being internal definitely causes the error. It is a good
> question whether it is a permanent change because there are pros and
> cons going both ways. Let me open a bug on this since it is
> something we need to make decision on. In the meantime, as a
> temporary workaround (emphas
Hello,
The example at www.ironpython.info 'The IronPython 2 Parser' does not seem
to work anymore with IP2A6...fails with a NameError: name 'Parser' is not
defined. I think it fails because Parser is now 'internal'? The question
I have is: Is this a permanent change - or is there another way
at the ironpython-differences doc). I also
looked through the source for IP (found the @returns and @accepts stuff),
and the source for the VS integration sample but could not decipher where
type definitions could be inside docstings/triple quoted strings.
Thanks,
David Lawler
When debugging an IronPython script I can see local variables in mdbg or
cordebug. However, I cannot find a way to get class (self) and module
variables. Is there anyway to do this? It's ok if it requires several
steps like going up the stack frame and finding a symbol reference and
then rea
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
mode, shove all the debugger related stuff in there, and then call it
from
my main thread.
David Lawler/FKS/FRANKE wrote on 09/18/2007 04:51:52 PM:
> I am experimenting and learning about debugging by playing with the
> source code to mdbg and the various samples.
> I thought it would
I am experimenting and learning about debugging by playing with the source
code to mdbg and the various samples.
I thought it would be fun to take the mdbg c# example program that prints
out modules as they are loaded and make a
version in IronPython (I tried IP 1.1 and 2.0A3):
import clr
clr.A
Thanks for your help (again) Dino. It turns out after a lot more playing
around that mdbg does work fairly well.
I found out that there is a bit more of a learning curve to mdbg than I
thought (who knew that you had to tell it which
thread to attach to for goodness sake)! Anyhow, I got it far e
Hi - Thanks Dave,
But while that shows how to embed Ironpython in Mdbg, I am looking to use
Mdbg to debug IronPython
programs/scripts. When I do this now with Clrdbg I can load the source
and step through it, set break points etc.
With Mdbg, if I use a self compiled version of Ironpython with t
I can debug IP 2 programs fairly nicely with clrdbg even setting break
points and examining variables but I have tried to get mdbg (and cordbg)
to work with no success. I am interested in mdbg because I would like to
learn more about how debugging support works with the clr and with IP in
part
Hi Dino,
Here it is. Thanks for taking a look at it.
"C:\Program Files\IronPython2A4\ipy.exe" -X:ExceptionDetail
-X:ShowClrExceptions "IronPythonDev.py"
ICSharpCode.TextEditor.Document.DefaultDocument.set_HighlightingStrategy(ICSharpCode.TextEditor.Document.IHighlightingStrategy)
at _stub_#
Yes I can - thanks for the quick reply!
>"C:\Program Files\IronPython2A4\ipy.exe" -X:ExceptionDetail
"IronPythonDev.py"
ICSharpCode.TextEditor.Document.DefaultDocument.set_HighlightingStrategy(ICSharpCode.TextEditor.Document.IHighlightingStrategy)
at _stub_##40(Object[] , DynamicSite`3 , CodeC
The following ugly hack works fine with IronPython 1.1 and with 2.0 alpha
3 but raises an exception on line 28 with IronPython 2.0 alpha 4.
To run this you need a copy of the ICSharpCode.TextEditor.dll from
SharpDevelop (http://www.icsharpcode.net/OpenSource/SD).
Is this a bug or a new 'feature'?
17 matches
Mail list logo