This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author stub
Recipients David MacIver, r.david.murray, stub
Date 2015-05-13.11:34:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Can we get this reopened? As David MacIver points out, this seems entirely a wart in tuple's constructor (compared to all the other builtin types), whereas 10977 is worrying about how 3rd party code using the C API can corrupt subclasses of builtin types (a much larger scope, and much less likely to be resolved in a good way).

Does it make sense to require python code wishing to case a tuple or tuple subclass do so using tuple(list(o)), or should tuple(o) work as expected? The primary use is of course converting a mutable sequence to an immutable representation to use as a dict key.
Date User Action Args
2015-05-13 11:34:01stubsetrecipients: + stub, r.david.murray, David MacIver
2015-05-13 11:34:00stubsetmessageid: <>
2015-05-13 11:34:00stublinkissue23757 messages
2015-05-13 11:34:00stubcreate