Well, it's only a problem if you need the parser module :) I've opened CodePlex work item 1347 for this - http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=1347 - it'll have to wait until after 1.0 at this point though because we're too close to the 1.0 release. We've also had a similar request for better quality checking tools support which rely on the parser module so this is starting to look more compelling. Thanks for reporting this.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of HEMMI, Shigeru Sent: Tuesday, July 25, 2006 12:19 AM To: Discussion of IronPython Subject: [IronPython] ImportError: No module named parser In IP, parser - an interface to Python's internal parser, is not implemented. Is it a problem or not? IronPython 1.0.60712 (Beta) on .NET 2.0.50727.42 Copyright (c) Microsoft Corporation. All rights reserved. >>> import parser Traceback (most recent call last): File , line 0, in <stdin>##3 File , line 0, in __import__##7 ImportError: No module named parser >>> _______________________________________________ users mailing list users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ users mailing list users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
