On 3/7/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mar 7, 2007, at 7:39 PM, Brett Cannon wrote:
>
> >> I think it's important to import on demand only though.
> >
> > And I agree.
>
> Cool.
>
> >> I should
> >> probably make that clear in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 7:39 PM, Brett Cannon wrote:
>> I think it's important to import on demand only though.
>
> And I agree.
Cool.
>> I should
>> probably make that clear in the PEP . IOW, "import email"
>> should not by side-effect import all sub-m
On 3/7/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mar 7, 2007, at 4:36 PM, Brett Cannon wrote:
>
> >> >> Third party package renaming is also supported, via several public
> >> >> interfaces accessible by any Python module.
> >> >>
> >> >
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 5:46 PM, BJörn Lindqvist wrote:
>> When Python's import machinery is initialized, the oldlib package is
>> imported. Inside oldlib there is a class called ``OldStdlibLoader``.
>> This class implements the PEP 302 interface and is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 4:36 PM, Brett Cannon wrote:
>> >> Third party package renaming is also supported, via several public
>> >> interfaces accessible by any Python module.
>> >>
>> >
>> > I guess a .pth file could install the mappings for the third-par
> When Python's import machinery is initialized, the oldlib package is
> imported. Inside oldlib there is a class called ``OldStdlibLoader``.
> This class implements the PEP 302 interface and is automatically
> instantiated, with zero arguments. The constructor reads all the
> ``.mv`` files from
On 3/6/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> >> Supported Renamings
> >> ===
> >>
> >> There are at least 4 use cases explicitly supported by this PEP:
> >>
> >> - - Simple top-level package name renamings, such as ``String
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 6, 2007, at 10:16 PM, [EMAIL PROTECTED] wrote:
> Does the proposed renaming include any restructuring (e.g. making
> hierarchies out of all or part of the stdlib where none existed
> before)? It
> wasn't obvious to me. For example, might th
Barry,
Does the proposed renaming include any restructuring (e.g. making
hierarchies out of all or part of the stdlib where none existed before)? It
wasn't obvious to me. For example, might there be a restructuring of the
entire stdlib?
Skip
___
Pyth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Supported Renamings
>> ===
>>
>> There are at least 4 use cases explicitly supported by this PEP:
>>
>> - - Simple top-level package name renamings, such as ``StringIO`` to
>>``stringio``;
>>
>> - - Sub-package renamings where th
On 3/6/07, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Here's a new PEP that's the outgrowth of work Brett Cannon and I did
> at PyCon. Basically we were looking for a way to allow for forward
> compatibility with PEP 3108, which describes a reorga
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here's a new PEP that's the outgrowth of work Brett Cannon and I did
at PyCon. Basically we were looking for a way to allow for forward
compatibility with PEP 3108, which describes a reorganization of the
standard library. PEP 364 is for Python
12 matches
Mail list logo
