On Tue, Jul 31, 2012 at 5:25 AM, PJ Eby wrote:
> On Mon, Jul 30, 2012 at 12:51 PM, Guido van Rossum wrote:
>> - Most importantly: calling len(obj) and catching TypeError can only
>> be a substitute for the real implementation, which IMO ought to check
>> for the presence of a tp_len slot. Alas, c
On Mon, Jul 30, 2012 at 12:51 PM, Guido van Rossum wrote:
> - Most importantly: calling len(obj) and catching TypeError can only
> be a substitute for the real implementation, which IMO ought to check
> for the presence of a tp_len slot. Alas, checking hasattr(obj,
> '__len__') doesn't quite cut i
If you give my second patch an LGTM I'll submit it and you're done.
On Mon, Jul 30, 2012 at 9:58 AM, Alex Gaynor wrote:
>
>
> On Mon, Jul 30, 2012 at 9:51 AM, Guido van Rossum wrote:
>>
>> Also, I have a few content quibbles:
>>
>> - Is it really worth flagging a negative return value with Value
On Mon, Jul 30, 2012 at 9:51 AM, Guido van Rossum wrote:
>
> Also, I have a few content quibbles:
>
> - Is it really worth flagging a negative return value with ValueError?
> I'd just as well clip this to zero. What's the worry? That the
> computed value is wrong? But it's only meant to be a hint,
On Sun, Jul 29, 2012 at 6:11 PM, Alex Gaynor wrote:
> Guido van Rossum python.org> writes:
>
>>
>>
>> Looks good to me, so accepted.But why isn't it visible on
>> python.org/dev/peps/
> yet?
>
> I just realized the text in the python.org repo did not match what I had
> locally.
> I've pushed wh
Guido van Rossum python.org> writes:
>
>
> Looks good to me, so accepted.But why isn't it visible on
> python.org/dev/peps/
yet?
I just realized the text in the python.org repo did not match what I had
locally.
I've pushed what I intended to be the latest text, if everyone could take a new
Hi Alex,
just a small info (view pep-0424.txt @ 4491:7838a83c3ad1):
- Section Proposal:
[...] than the actual size >>> ofthe <<< container. [...]
- Section Rationale:
The first line is really long (seems to need a newline before
``__length_hint__``)
Regards
francis
___
But why isn't it visible on python.org/dev/peps/ yet?
Because the build process of the PEPs broke when hg.python.org became
its own system.
I'll try to look into that tomorrow, since unfortunately nobody else
volunteered
to fix it.
Regards,
Martin
__
On Sat, 28 Jul 2012 17:05:01 + (UTC)
Alex Gaynor wrote:
> Hi all,
>
> The discussion on PEP 0424 seems to have subsided (and I haven't gotten angry
> emails in a week!). So I would like to request a BDFL or BDFP pronouncement
> on PEP 0424, text available here:
> http://hg.python.org/peps/
2012/7/28 Guido van Rossum :
> Looks good to me, so accepted.
>
> But why isn't it visible on python.org/dev/peps/ yet?
The rebuilding hook is broken.
--
Regards,
Benjamin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailm
Looks good to me, so accepted.
But why isn't it visible on python.org/dev/peps/ yet?
On Sat, Jul 28, 2012 at 7:37 PM, Guido van Rossum wrote:
> I'll pronounce. Give me a few days.
>
> On Sat, Jul 28, 2012 at 10:05 AM, Alex Gaynor
> wrote:
> > Hi all,
> >
> > The discussion on PEP 0424 seems to
I'll pronounce. Give me a few days.
On Sat, Jul 28, 2012 at 10:05 AM, Alex Gaynor wrote:
> Hi all,
>
> The discussion on PEP 0424 seems to have subsided (and I haven't gotten angry
> emails in a week!). So I would like to request a BDFL or BDFP pronouncement
> on PEP 0424, text available here:
>
Hi all,
The discussion on PEP 0424 seems to have subsided (and I haven't gotten angry
emails in a week!). So I would like to request a BDFL or BDFP pronouncement
on PEP 0424, text available here:
http://hg.python.org/peps/file/tip/pep-0424.txt
Alex
_
13 matches
Mail list logo
