nd also in the next release.
Thanks for a great repro!
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, November 28, 2007 1:46 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Parser is not accessible
> 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
resolution.
Thanks for the feedback!
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, November 27, 2007 1:19 PM
To: Discussion of IronPython
Subject: [IronPython] Parser is not accessible anymore in IP2A6
Hello
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
