In article
,
Brett Cannon wrote:
> On Fri, Sep 27, 2013 at 5:16 PM, Zachary Ware
> wrote:
> > The way I read Terry's proposal, it is to never add the _ensurepip
> > *module*, but to use (or make available, whichever makes sense in a
> > given case) the _ensurepip *script* when it is requested at
On Mon, Sep 23, 2013 at 2:15 PM, Nick Coghlan wrote:
> With the last round of updates, I believe PEP 453 is ready for
> Martin's pronouncement.
>
> HTML: http://www.python.org/dev/peps/pep-0453/
> Major diffs: http://hg.python.org/peps/rev/b2993450b32a
I'd enjoy concise PEP texts, but it is extre
On Sat, 28 Sep 2013 15:59:05 +1000
Nick Coghlan wrote:
> It sounds like a reasonable approach to me.
>
> In terms of naming, would you consider "concurrent.asyncio"? When we
> created that parent namespace for futures, one of the other suggested
> submodules discussed was the standard event loop
On Fri, Sep 27, 2013 at 6:19 PM, Benjamin Peterson wrote:
> 2013/9/27 Barry Warsaw :
> > On Sep 26, 2013, at 02:30 PM, Nick Coghlan wrote:
> >
> >>- the module name should be "_ensurepip" in all versions
> >>- the PEP should explicitly state that the "don't remove _ensurepip
> >>and it's wheel fil
On Sep 27, 2013, at 09:14 PM, Brett Cannon wrote:
>I don't see any issue with redirecting the discussion. python-tulip@ is
>acting like a SIG for the module, so no real precedent beyond it not being
>hosted as a mail.python.org list.
The PEP process even allows for this formally. Please add a D
On Sep 28, 2013, at 12:48 PM, Stephen J. Turnbull wrote:
>*shrug* I just think the risks are higher than acknowledged (just
>because you have so far failed to imagine a problem doesn't mean it
>won't appear), and that the meta effect that "Even Guido admits that
>Python 3 isn't ready for prime ti
Hi, I just downloaded Python 3.3 top teach myself how to program, I am
new to programming, but the guide I am using requires me to access the
toolbar, which I cannot seem to find. How do I find it and have it
displayed on the interface? I tried v 3.1 but its still absent. Thank
you.
___
On Fri, Sep 27, 2013 at 3:33 PM, Guido van Rossum wrote:
> I've been looking at my progress with Tulip and the 3.4 release schedule
> (PEP 429) and it looks like I will have to do some kind of sprint to get it
> into the release in time for beta 1, which is planned for Nov 24. Ideally
> I'd get i
On 9/28/2013 7:28 AM, Kevin Ngugi wrote:
Hi, I just downloaded Python 3.3 top teach myself how to program, I am
new to programming, but the guide I am using requires me to access the
toolbar, which I cannot seem to find. How do I find it and have it
displayed on the interface? I tried v 3.1 but i
On 28/09/2013 12:28, Kevin Ngugi wrote:
Hi, I just downloaded Python 3.3 top teach myself how to program, I am
new to programming, but the guide I am using requires me to access the
toolbar, which I cannot seem to find. How do I find it and have it
displayed on the interface? I tried v 3.1 but it
On Fri, Sep 27, 2013 at 10:59 PM, Nick Coghlan wrote:
> It sounds like a reasonable approach to me.
>
> In terms of naming, would you consider "concurrent.asyncio"? When we
> created that parent namespace for futures, one of the other suggested
> submodules discussed was the standard event loop A
> On Sep 28, 2013, at 12:59 AM, Nick Coghlan wrote:
>
> It sounds like a reasonable approach to me.
>
> In terms of naming, would you consider "concurrent.asyncio"? When we created
> that parent namespace for futures, one of the other suggested submodules
> discussed was the standard event l
On Sat, Sep 28, 2013 at 9:07 AM, Eli Bendersky wrote:
>
>
> Sounds good. But once it's in stdlib, I think it would be proper to shift
> the discussion into the normal pydev channels (python-dev, issue tracker,
> etc.). Is this the plan?
>
Hadn't really thought about that. I think there's a preced
On 28/09/2013 12:28, Kevin Ngugi wrote:
Hi, I just downloaded Python 3.3 top teach myself how to program, I am
new to programming, but the guide I am using requires me to access the
toolbar, which I cannot seem to find. How do I find it and have it
displayed on the interface? I tried v 3.1 but it
On 9/22/2013 10:44 PM, Guido van Rossum wrote:
On Sun, Sep 22, 2013 at 7:25 PM, Terry Reedy
('Return' rather than 'Returns' is the current convention.)
That's actually a religious argument which in the stdlib takes no strict
position -- a quick grep shows that both are used, although 'R
On 29 Sep 2013 02:52, "Guido van Rossum" wrote:
>
> On Fri, Sep 27, 2013 at 10:59 PM, Nick Coghlan wrote:
>>
>> It sounds like a reasonable approach to me.
>>
>> In terms of naming, would you consider "concurrent.asyncio"? When we
created that parent namespace for futures, one of the other sugges
16 matches
Mail list logo
