gh-141218: Fix inaccurate object comparison documentation

[mohsinm-dev]

Summary

Fixes issue #141218 by correcting inaccurate documentation about object comparison.

Problem: The current documentation states "Objects of different types, except different numeric types, never compare equal" which is factually incorrect.

Counter-example:

>>> frozenset([1, 2]) == {1, 2}
True

Solution: Changed to "Objects of different types, unless documented otherwise, never compare equal" to account for all documented exceptions.

Documented exceptions include:

• Numeric types (int, float, complex) - already mentioned
• set/frozenset comparisons - documented later in same file
• dict subclass comparisons (defaultdict, Counter, OrderedDict)

Changes

• Updated Doc/library/stdtypes.rst line 167
• Added news entry in Misc/NEWS.d/next/Documentation/

Test plan

• Documentation builds successfully with make html
• Verified change maintains consistency with existing specific type documentation
• Tested that the issue examples work as described
• Confirmed change is minimal and maintains readability

The fix improves documentation accuracy while maintaining clarity and consistency.

• Issue: Rephrase general rules for comparison of objects #141218

---

📚 Documentation preview 📚: https://cpython-previews--141221.org.readthedocs.build/

[python-cla-bot]

All commit authors signed the Contributor License Agreement.

[OTheDev]

Suggested change

	exceptions like set/frozenset comparisons.
	exceptions like set/frozenset comparisons.

To fix the lint error

[skirpichev]

I suggest just revert news. Its usually not required for docs changes.