From ericsnowcurrently at gmail.com  Wed Oct  2 23:25:39 2013
From: ericsnowcurrently at gmail.com (Eric Snow)
Date: Wed, 2 Oct 2013 15:25:39 -0600
Subject: [Import-SIG] latest update of PEP 451
In-Reply-To: <CAP1=2W4G012+V21zKEsvApnJ5x0PiYOj4oHcfVC0TrOr6DyX7w@mail.gmail.com>
References: <CALFfu7AbpBYe-YxoBHS6jCjTdz9KLW4EPruHXNmgD3vpgftTKQ@mail.gmail.com>
 <CAP1=2W4G012+V21zKEsvApnJ5x0PiYOj4oHcfVC0TrOr6DyX7w@mail.gmail.com>
Message-ID: <CALFfu7AW_5E12YdBSth6OjufVPwaLpFPzLg4CNp0WQZE2ebgew@mail.gmail.com>

FYI, I've updated the PEP and hope to wrap up an initial patch in the
next day or two.  Unless anyone here objects, once I have the patch up
I'm going to post the PEP to python-dev and try to get everything
wrapped up ASAP (3.4-alpha4 is on Oct.20).

If that goes smoothly, does anyone think it will be a bad idea to try
to get the .ref file PEP in for 3.4?  While beta1 is in less than 2
months, the PEP is smaller, less invasive, we'd already hashed out the
details, and ModuleSpec addresses the implementation issue we had.
The only roadblock that I see is my crazy schedule, but given where we
left .ref files, I think it is doable.  With that in mind, once I've
pushed PEP 451 to python-dev I'll probably revisit the .ref PEP, get
it a number, and crank on the implementation.  Thoughts?

-eric

p.s. I've given up on C OrderedDict and friends for 3.4 in favor of
these 2 import PEPS.  They're worth it though.  Thanks for convincing
me to work on them, Nick! :)

On Wed, Sep 25, 2013 at 7:05 AM, Brett Cannon <brett at python.org> wrote:
[snipped feedback]

From brett at python.org  Wed Oct  2 23:29:07 2013
From: brett at python.org (Brett Cannon)
Date: Wed, 2 Oct 2013 17:29:07 -0400
Subject: [Import-SIG] latest update of PEP 451
In-Reply-To: <CALFfu7AW_5E12YdBSth6OjufVPwaLpFPzLg4CNp0WQZE2ebgew@mail.gmail.com>
References: <CALFfu7AbpBYe-YxoBHS6jCjTdz9KLW4EPruHXNmgD3vpgftTKQ@mail.gmail.com>
 <CAP1=2W4G012+V21zKEsvApnJ5x0PiYOj4oHcfVC0TrOr6DyX7w@mail.gmail.com>
 <CALFfu7AW_5E12YdBSth6OjufVPwaLpFPzLg4CNp0WQZE2ebgew@mail.gmail.com>
Message-ID: <CAP1=2W4v5SUxAuQKoEJ=6+mS0qfRj8Z6-BE7n=Xuw-7B3tsnNw@mail.gmail.com>

On Wed, Oct 2, 2013 at 5:25 PM, Eric Snow <ericsnowcurrently at gmail.com>wrote:

> FYI, I've updated the PEP and hope to wrap up an initial patch in the
> next day or two.  Unless anyone here objects, once I have the patch up
> I'm going to post the PEP to python-dev and try to get everything
> wrapped up ASAP (3.4-alpha4 is on Oct.20).
>
> If that goes smoothly, does anyone think it will be a bad idea to try
> to get the .ref file PEP in for 3.4?  While beta1 is in less than 2
> months, the PEP is smaller, less invasive, we'd already hashed out the
> details, and ModuleSpec addresses the implementation issue we had.
> The only roadblock that I see is my crazy schedule, but given where we
> left .ref files, I think it is doable.  With that in mind, once I've
> pushed PEP 451 to python-dev I'll probably revisit the .ref PEP, get
> it a number, and crank on the implementation.  Thoughts?
>

If you can still turn out a quality PEP then I don't see any explicit issue.

-Brett


>
> -eric
>
> p.s. I've given up on C OrderedDict and friends for 3.4 in favor of
> these 2 import PEPS.  They're worth it though.  Thanks for convincing
> me to work on them, Nick! :)
>
> On Wed, Sep 25, 2013 at 7:05 AM, Brett Cannon <brett at python.org> wrote:
> [snipped feedback]
> _______________________________________________
> Import-SIG mailing list
> Import-SIG at python.org
> https://mail.python.org/mailman/listinfo/import-sig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/import-sig/attachments/20131002/8ea2e381/attachment.html>

From ncoghlan at gmail.com  Thu Oct  3 01:58:24 2013
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Thu, 3 Oct 2013 09:58:24 +1000
Subject: [Import-SIG] latest update of PEP 451
In-Reply-To: <CAP1=2W4v5SUxAuQKoEJ=6+mS0qfRj8Z6-BE7n=Xuw-7B3tsnNw@mail.gmail.com>
References: <CALFfu7AbpBYe-YxoBHS6jCjTdz9KLW4EPruHXNmgD3vpgftTKQ@mail.gmail.com>
 <CAP1=2W4G012+V21zKEsvApnJ5x0PiYOj4oHcfVC0TrOr6DyX7w@mail.gmail.com>
 <CALFfu7AW_5E12YdBSth6OjufVPwaLpFPzLg4CNp0WQZE2ebgew@mail.gmail.com>
 <CAP1=2W4v5SUxAuQKoEJ=6+mS0qfRj8Z6-BE7n=Xuw-7B3tsnNw@mail.gmail.com>
Message-ID: <CADiSq7fr3yJ3OPFTqsSfNZw3gDkEWzShr=-_+33x44jbjHFbCA@mail.gmail.com>

On 3 Oct 2013 07:29, "Brett Cannon" <brett at python.org> wrote:
>
>
>
>
> On Wed, Oct 2, 2013 at 5:25 PM, Eric Snow <ericsnowcurrently at gmail.com>
wrote:
>>
>> FYI, I've updated the PEP and hope to wrap up an initial patch in the
>> next day or two.  Unless anyone here objects, once I have the patch up
>> I'm going to post the PEP to python-dev and try to get everything
>> wrapped up ASAP (3.4-alpha4 is on Oct.20).
>>
>> If that goes smoothly, does anyone think it will be a bad idea to try
>> to get the .ref file PEP in for 3.4?  While beta1 is in less than 2
>> months, the PEP is smaller, less invasive, we'd already hashed out the
>> details, and ModuleSpec addresses the implementation issue we had.
>> The only roadblock that I see is my crazy schedule, but given where we
>> left .ref files, I think it is doable.  With that in mind, once I've
>> pushed PEP 451 to python-dev I'll probably revisit the .ref PEP, get
>> it a number, and crank on the implementation.  Thoughts?
>
>
> If you can still turn out a quality PEP then I don't see any explicit
issue.

I realised the existing *.pth mechanism is a better fit for my original use
case (sharing distributions between virtual environments), but *.ref files
would still be useful as platform neutral symlinks for dev environments and
selective path overrides. So +1 if you can find the time, but don't stress
if it slips to 3.5.

Cheers,
Nick.

>
> -Brett
>
>>
>>
>> -eric
>>
>> p.s. I've given up on C OrderedDict and friends for 3.4 in favor of
>> these 2 import PEPS.  They're worth it though.  Thanks for convincing
>> me to work on them, Nick! :)
>>
>> On Wed, Sep 25, 2013 at 7:05 AM, Brett Cannon <brett at python.org> wrote:
>> [snipped feedback]
>> _______________________________________________
>> Import-SIG mailing list
>> Import-SIG at python.org
>> https://mail.python.org/mailman/listinfo/import-sig
>
>
>
> _______________________________________________
> Import-SIG mailing list
> Import-SIG at python.org
> https://mail.python.org/mailman/listinfo/import-sig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/import-sig/attachments/20131003/3bb7aa32/attachment.html>

From ericsnowcurrently at gmail.com  Sat Oct  5 07:22:26 2013
From: ericsnowcurrently at gmail.com (Eric Snow)
Date: Fri, 4 Oct 2013 23:22:26 -0600
Subject: [Import-SIG] latest update of PEP 451
In-Reply-To: <CADiSq7fr3yJ3OPFTqsSfNZw3gDkEWzShr=-_+33x44jbjHFbCA@mail.gmail.com>
References: <CALFfu7AbpBYe-YxoBHS6jCjTdz9KLW4EPruHXNmgD3vpgftTKQ@mail.gmail.com>
 <CAP1=2W4G012+V21zKEsvApnJ5x0PiYOj4oHcfVC0TrOr6DyX7w@mail.gmail.com>
 <CALFfu7AW_5E12YdBSth6OjufVPwaLpFPzLg4CNp0WQZE2ebgew@mail.gmail.com>
 <CAP1=2W4v5SUxAuQKoEJ=6+mS0qfRj8Z6-BE7n=Xuw-7B3tsnNw@mail.gmail.com>
 <CADiSq7fr3yJ3OPFTqsSfNZw3gDkEWzShr=-_+33x44jbjHFbCA@mail.gmail.com>
Message-ID: <CALFfu7AZCTgL175Lc6WNDo94Z6r5toxn7bTQVXxOx1sBLhV6Wg@mail.gmail.com>

On Wed, Oct 2, 2013 at 5:58 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> I realised the existing *.pth mechanism is a better fit for my original use
> case (sharing distributions between virtual environments), but *.ref files
> would still be useful as platform neutral symlinks for dev environments and
> selective path overrides. So +1 if you can find the time, but don't stress
> if it slips to 3.5.

In that case I'm going to push this off until 3.5.  :)  It's not worth
rushing it at this point even if it's already close, which I may be
misremembering. :)

-eric