ehalf Of Michael Foord
Sent: Monday, December 15, 2008 3:04 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Compiled dlls and builtin modules
Dino Viehland wrote:
>
> I think this behavior is currently by design because we're using
> sys.meta_path which does take precedenc
m] On Behalf Of Curt Hagenlocher
Sent: Monday, December 15, 2008 3:50 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Compiled dlls and builtin modules
Sounds waaay too easy :P.
In the long run, I'd prefer that we implement only the "C" part of these
modules and share the Pyth
Sounds waaay too easy :P.
In the long run, I'd prefer that we implement only the "C" part of these
modules and share the Python part with CPython. But this is not only a
potentially breaking change, it also would require modification to the
standard library for at least the "socket" module.
On Mo
thon
*Subject:* [IronPython] Compiled dlls and builtin modules
Hi all,
We are compiling the python standard library (so it can be ngend when
it is shipped with Resolver One) and we've discovered that modules in
the dll take precedence over builtins. We noticed this because re and
socket are in
lto:users-boun...@lists.ironpython.com] On Behalf Of Glenn Jones
Sent: Friday, December 12, 2008 8:27 AM
To: Discussion of IronPython
Subject: [IronPython] Compiled dlls and builtin modules
Hi all,
We are compiling the python standard library (so it can be ngend when it is
shipped with Resolver One) and we'
Hi all,
We are compiling the python standard library (so it can be ngend when it is
shipped with Resolver One) and we've discovered that modules in the dll take
precedence over builtins. We noticed this because re and socket are included
in the standard Lib directory (installed with IPy2) and when
