List and deque disagree on what __init__ does. Which one is
right?
Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit (Intel)] on
win32
Type help, copyright, credits or license for more information.
from collections import deque
x = deque([0, 1])
x.__init__([2, 3])
x
I agree that the behavior should be more consistant, but you also
should not be calling __init__ more than once on any given instance
and that in and of itself should probably constitute undefined behavior.
On Dec 12, 2007, at 3:22 PM, Neil Cerutti wrote:
List and deque disagree on what
On 2007-12-12, Calvin Spealman [EMAIL PROTECTED] wrote:
I agree that the behavior should be more consistant, but you
also should not be calling __init__ more than once on any
given instance and that in and of itself should probably
constitute undefined behavior.
That seems wise to me, too,
On Dec 12, 7:22 am, Neil Cerutti [EMAIL PROTECTED] wrote:
List and deque disagree on what __init__ does. Which one is
right?
File a bug report and assign to me.
Raymond
--
http://mail.python.org/mailman/listinfo/python-list
On Dec 12, 2007, at 4:05 PM, Neil Cerutti wrote:
On 2007-12-12, Calvin Spealman [EMAIL PROTECTED] wrote:
I agree that the behavior should be more consistant, but you
also should not be calling __init__ more than once on any
given instance and that in and of itself should probably
On Dec 12, 8:41 am, Calvin Spealman [EMAIL PROTECTED]
wrote:
It documents that deque.__init__ initializes it, as all __init__
methods do. All init methods are also assumed to _only_ be called at
the start of the life of the object and never more than once, so
breaking that breaks assumption
On 2007-12-12, Raymond Hettinger [EMAIL PROTECTED] wrote:
On Dec 12, 7:22 am, Neil Cerutti [EMAIL PROTECTED] wrote:
List and deque disagree on what __init__ does. Which one is
right?
File a bug report and assign to me.
Will do. Registration in progress.
--
Neil Cerutti
--
