> A well-known trick is applicable in that case, if Martin thinks it's
> worth the bother:
> grow the list to its final size once, at the start (overestimating if
> you don't know for sure). Then instead of appending, keep an index to
> the next free slot, same as you'd do in C. Then the list gut
Reinhold Birkenfeld wrote:
> Hello,
>
> this time working up some of the patches with beards:
No one listening? I'm sorry when patch reviews are not welcome in
python-devel; in this case I'll post individual comments to the patches
on SF.
Reinhold
___
On Wed, Feb 23, 2005, Reinhold Birkenfeld wrote:
> Reinhold Birkenfeld wrote:
>>
>> this time working up some of the patches with beards:
>
> No one listening? I'm sorry when patch reviews are not welcome in
> python-devel; in this case I'll post individual comments to the patches
> on SF.
You s
Aahz wrote:
> On Wed, Feb 23, 2005, Reinhold Birkenfeld wrote:
>> Reinhold Birkenfeld wrote:
>>>
>>> this time working up some of the patches with beards:
>>
>> No one listening? I'm sorry when patch reviews are not welcome in
>> python-devel; in this case I'll post individual comments to the pat
While rummaging in the old patches, I found this:
"""
The result of the PyCore sprint of me and Brett: the CALL_ATTR opcode
(LOAD_ATTR and CALL_FUNCTION combined) that skips the PyMethod creation
and destruction for classic classes (but not newstyle classes, yet.)
The code is somewhat rough yet,
Reinhold Birkenfeld wrote:
While rummaging in the old patches, I found this:
"""
The result of the PyCore sprint of me and Brett: the CALL_ATTR opcode
(LOAD_ATTR and CALL_FUNCTION combined) that skips the PyMethod creation
and destruction for classic classes (but not newstyle classes, yet.)
The cod
In a recent discussion in a SF patch, I noticed that PEP 328* only seems
to support relative imports within packages, while bare import
statements use the entirety of sys.path, not solving the shadowing of
standard library module names.
I have certainly forgotten bits of discussion from last spri
Reinhold Birkenfeld wrote:
No one listening? I'm sorry when patch reviews are not welcome in
python-devel; in this case I'll post individual comments to the patches
on SF.
I have seen them, and I appreciate them, but I had no time to respond,
yet (likewise for the 20+ other reviews which I still ne
> In a recent discussion in a SF patch, I noticed that PEP 328* only seems
> to support relative imports within packages, while bare import
> statements use the entirety of sys.path, not solving the shadowing of
> standard library module names.
Hm. I'm not convinced that there is a *problem* with
Walter Dörwald wrote:
M.-A. Lemburg wrote:
Walter Dörwald wrote:
M.-A. Lemburg wrote:
> [...]
__str__ and __unicode__ as well as the other hooks were
specifically added for the type constructors to use.
However, these were added at a time where sub-classing
of types was not possible, so it's time
10 matches
Mail list logo
