It might be interesting to also run with -X:ExceptionDetail to see where the exception is coming from and report that back to the Mono team.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Haibo Luo Sent: Tuesday, January 23, 2007 9:05 AM To: Discussion of IronPython Subject: Re: [IronPython] Problems with -X:SaveAssemblies I did not see the repro in ironpython + .net. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo Sent: Monday, January 22, 2007 11:26 PM To: Discussion of IronPython Subject: [IronPython] Problems with -X:SaveAssemblies I found this while testing precompiled module feature, but it's the same with plain 1.1a1. I'm not sure whether this is IronPython problem. Can anyone confirm this on .NET, not Mono? How to reproduce: 1. Create x/__init__.py and y/__init__.py as empty files. 2. Create z.py with content "import x, y". 3. Run z.py with and without -X:SaveAssemblies. Later produces null point exception for me. -- Seo Sanghyeon _______________________________________________ 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
