Matthew Russell added the comment:
Yes, the output is fishy indeed my bad (paste error).
Tim: I hadn't thought for long enough or thought to check with the id builtin -
nice catch.
--
status: open -> closed
___
Python tracke
New submission from Matthew Russell :
Tuples, as we know are designed to immutable.
Hence I'm questioning if the following behavior is considered a defect:
>>> t = (1, 2)
>>> t += (1, 2, 3)
>>> t
(1, 2, 3)
?
--
components: Interpreter Core
messages:
Changes by Matthew Russell :
--
title: Depricate iterable.next in Python > 2.6.x when called with -3 option ->
Deprecate iterable.next in Python > 2.6.x when called with -3 option ?
___
Python tracker
<http://bugs.python.o
New submission from Matthew Russell :
Not sure if this should be (tentative) feature request or behavior...
It might help new comers and those preparing to port to Python 3.
--
assignee: georg.brandl
components: 2to3 (2.x to 3.0 conversion tool), Documentation, Interpreter Core
Changes by Matthew Russell:
--
components: Interpreter Core, Library (Lib)
files: py3k_bug1.txt
severity: urgent
status: open
title: itertools missing, causes interactive help to break
type: behavior
versions: Python 3.0
__
Tracker <[EMAIL PROTEC
