fully load faster since they will be interpreted
import someLargeModule1
import someLargeModule2
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Eloff
Sent: Wednesday, June 25, 2008 9:11 AM
To: Discussion of IronPython
Subject: Re: [IronP
#x27;ll be a combination of many things that ultimately speeds this up. Sorry
> it won't get immediately better - I'm as unhappy about it as you :(.
>
> -Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Eloff
> Sent: Tuesday, June 24
Dino Viehland wrote:
There's a couple of plans a foot. We have been working on a pre-compilation feature like .pyc for IronPython 2.0 It's actually in Beta 3 but unfortunately it doesn't quite work yet which is the reason we haven't said anything. It will be there (and working!) in beta 4.
lf Of Dan Eloff
Sent: Tuesday, June 24, 2008 5:58 PM
To: Discussion of IronPython
Subject: Re: [IronPython] The slow part of IronPython
> There's a couple of plans a foot. We have been working on a pre-compilation
> feature like .pyc for IronPython 2.0 It's actually in Beta 3 but
&
> There's a couple of plans a foot. We have been working on a pre-compilation
> feature like .pyc for IronPython 2.0 It's actually in Beta 3 but
> unfortunately it doesn't quite work yet which is the reason we haven't said
> anything. It will be there (and working!) in beta 4.
Wow, looking f
There's a couple of plans a foot. We have been working on a pre-compilation
feature like .pyc for IronPython 2.0 It's actually in Beta 3 but unfortunately
it doesn't quite work yet which is the reason we haven't said anything. It
will be there (and working!) in beta 4. That's the short term