[IronPython] Interesting problems with compiling IP2 programs....
srivatsn at microsoft.com
Fri Aug 8 13:48:32 PDT 2008
Looks like this has already been fixed in the latest sources. This reproes with the beta4 binaries but works fine with the latest binaries from our depot (once I have thrown in stat.py and userdict.py anyway). There was an import related checkin that went in this Monday. That might have fixed this I believe. The latest sources are up on codeplex. So if you wish you could sync and try it out. Thanks for reporting this.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of David.Lawler at franke.com
Sent: Friday, August 08, 2008 7:58 AM
To: Discussion of IronPython
Subject: [IronPython] Interesting problems with compiling IP2 programs....
Unfortunately, now you will be 'punished' for releasing pyc.py. The
following code does some funny things when compiled:
This works fine if you launch it as a script with IP2. You get:
C:\Documents and Settings\LD003\My Documents\Python
2.5.0 (IronPython 2.0 Beta (22.214.171.12400) on .NET 2.0.50727.1433)
>Exit code: 0
If you compile it and shove os.py and ntpath.py into the directory it
lives in (along with the required dll's)....
and then the program hangs....eats memory....and eventually dies with a
if you comment out import os, print "3", print os.getcwd() you get:
not exactly the same result. For me this is not an urgent fix....for
other folks....you are warned.
Users mailing list
Users at lists.ironpython.com
More information about the Users