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
Dino Viehland wrote:
I think this behavior is currently by design because we’re using
sys.meta_path which does take precedence over the built-in modules. We
could switch to using sys.path_hooks in 2.1 or 3.0 if the consensus is
this behavior in undesirable (which would also give control over
I think this behavior is currently by design because we're using sys.meta_path
which does take precedence over the built-in modules. We could switch to using
sys.path_hooks in 2.1 or 3.0 if the consensus is this behavior in undesirable
(which would also give control over when pre-compiled modul
