tim wrote:
> [Greg Stein]
> > Regardless: yes, it can certainly break some code. IMO, if any code =
out
> > there makes any kinds of assumptions about id(), then they deserve =
to be
> > broken :-)
>=20
> [Trent Mick]
> > Amen.
>=20
> Guys, it's almost never that simple, and developers are the last ones =
to
> think of the reasonable cases that may break.
especially since it's documented to be an integer:
id (object)=20
Return the `identity' of an object. This is an integer which is
guaranteed to be unique and constant for this object during
its lifetime.
(section 2.1.4 says that "integer" is the same thing as a "plain
integer", and that "long integer" is something different).
</F>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4