Raymond Hettinger added the comment: > Ah... "be the same object or compare equal" sounds much better.
Yes, the plain language is clear and reads nicely. > We can't say "will normally", since we don't know about > the infinite number of possible container types that people > might create. The most we can say is that *builtin* container > types will [assuming that this is the intent] or that general > containers *may*. "general containers may" is most accurate. > Several suggested changes: Jim, can you propose a much more minimal edit? As you pointed-out, the underlying logic is "containers are permitted to (and generally do) read "same as" as "is or __eq__". I don't think we should say much more than that in the section on expressions. Any notes on NaNs should probably be in a section talking about the float type. The weirdness of NaNs is a feature of the NaNs, not a feature of the entire language. We definitely don't want a NaN note added to the documentation of every container. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22001> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
