Dino Viehland wrote: > Ok, I closed 12908 as a dup. If there's no info on it we can always try > reverse engineering it (or see if test_codeop fails when we just ignore the > flag instead of throwing - that might be the simplest thing to do). >
I've already tried not using the flag and it causes some odd behaviour (try my interactive interpreter in the browser with a function with several lines inside the body of the function): http://www.voidspace.org.uk/ironpython/silverlight-console/console.html So I don't think just ignoring it will work. I also took a look at the C (pythonrun.c) but I don't speak C. :-( I've asked one of the core developers for help, so we'll see what he comes back with. I'm also playing with the code in the DLRConsole as a temporary workaround - but it would be nice to get this working. Michael http://www.manning.com/foord > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord > Sent: Friday, September 21, 2007 1:23 PM > To: Discussion of IronPython > Subject: Re: [IronPython] [python] Re: Missing Compiler Flag > > Dino Viehland wrote: > >> Strangely it doesn't seem to be in the documentation for compile() either :( >> >> Do you know what this option does by any chance :) ? >> >> I've opened bug #12908 >> > > Great - it can go with 12907. :-) > > It is something to do with dedenting. ;-) > > I can't find much about it on the intarwebz. It is defined in > pythonrun.h and seems to be used in pythonrun.c and it is involved with > parsing which makes sense. > > I'll try asking around. *sigh* > > Michael Foord > http://www.manning.com/foord > > >> (http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=12908) so >> we at least have it tracked... >> >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord >> Sent: Friday, September 21, 2007 12:57 PM >> To: Discussion of IronPython >> Subject: [IronPython] Missing Compiler Flag >> >> Hello all, >> >> There's another problem with the interactive interpreter in IronPython >> (it affects the ability to use the code standard library module). >> >> The PyCF_DONT_IMPLY_DEDENT compiler flag is not recognised in IronPython. >> >> The flag is defined in the 'codeop' standard library module: >> >> PyCF_DONT_IMPLY_DEDENT = 0x200 # Matches pythonrun.h >> >> Attempting to use this in IronPython: >> >> >>> compile('print x', 'test', 'single', 0x200, 1) >> Traceback (most recent call last): >> File , line 0, in <stdin>##1 >> File , line 0, in Compile##4 >> ValueError: unrecognized flags >> >> Without this flag the code module can't recognize blocks of code with >> several indented lines. :-( >> >> All the best, >> >> >> Michael Foord >> http://www.manning.com/foord >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com >> >> >> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > _______________________________________________ > Users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > > _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
