You could consider accomplishing the same thing in the 
footnotes area, but I didn't see any reason to make the 
reader jump around for this info.

Logged In: YES 
user_id=3066

This report is very vague.  What part of the documentation
are you referring to, and how do you think it should be changed.

Logged In: YES 
user_id=52572

I think I originally tried to attach a patch which SF dropped 
due to one of its usual bugs.   I think the question was 
whether d[k] = y would unconditionally set the identity of the 
key object in d to k, or whether any previous equal key in 
that "slot" would be preserved.  It's the latter, and the 
current docs don't say which one it is.

Logged In: YES 
user_id=99874

I asked about this on python-dev. Turns out that the
behavior is the same in CPython and Jython (at least), but
that it is officially undefined in the language (ie, if
someone finds a more efficient way to implement a dict which
happens to alter what happens when assigning to existing
keys, then it might change). Therefore, I think it should
NOT be documented. It's rare that people would create
objects that compare equal and yet care which one is used,
and anyone doing so should know what they're doing well
enough to test it out.

Logged In: YES 
user_id=6656

I agree.  Closing.