[Anthony Baxter]
Ok, so here's the state of play: 2.3.5 is currently aimed for next
Tuesday, but there's an outstanding issue - the new copy code appears
to have broken something, see www.python.org/sf/1114776 for the gory
details.
...
[Alex Martelli]
The problem boils down to: deepcopying
On Sun, 6 Feb 2005 10:49:05 -0600, Skip Montanaro [EMAIL PROTECTED] wrote:
Wouldn't it be better to have the peephole optimizer recognize the throwaway
nature of lists in these contexts:
for elt in [1, 2, 4, 8, 16]:
...
if foo in [list, tuple]:
...
(anywhere
[Neal]
I think I implemented this once. I'll try to see if I can find a
patch. It wasn't too difficult, but I'm not sure if the patch was
clean.
If the opportunity arises, another worthwhile peepholer buildout would
be to recognize if-elif chains that can be transformed to a single
lookup
Modified Files:
Tag: release23-maint
test_copy.py
Log Message:
fix bug 1114776
Don't forget release24-maint.
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
Raymond [Skip]
If lists are conceptually like vectors or arrays in other languages
and tuples are like C structs or Pascal records, then by converting
from list to tuple form you've somehow muddied the data structure
water just to take advantage of tuples' immutability.
Any objections to replacing the likes of types.IntType and
types.ListType with int and list?
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
