[issue34972] json dump silently converts int keys to string

[Stuart Bishop]

Stuart Bishop  added the comment:

(sorry, my example is normal Python behavior. {1:1, 1.0:2} == {1:2} , {1.0:1} 
== {1:1} )

--
nosy: +stub

___
Python tracker 
<https://bugs.python.org/issue34972>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24773] Implement PEP 495 (Local Time Disambiguation)

[Stuart Bishop]

Changes by Stuart Bishop <stu...@stuartbishop.net>:


--
nosy: +stub

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue24773>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23757] tuple function gives wrong answer when called on list subclass with custom __iter__

[Stuart Bishop]

Stuart Bishop added the comment:

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.

--
nosy: +stub

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23757
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com