Christopher Barker wrote: > Sean Gillies wrote: >> How many of you use >> >> 1) a == b >> >> to test for topological equality instead of using >> >> 2) a.equals(b) > > I don't have any production Shapely code (yet), so a change is fine, but > I'm interested in more detail: > >> 1 is stronger than, but implies 2. 2 does not imply 1. > > So what is the difference that you propose? What other definitions of > equality do you want to support? > > -Chris >
No others. Early on it seemed "nice" to let GIS users check for topological equality using the == operator. But it turns out that it's actually harmful. More often, as Eric Lemoine showed me with the SQLAlchemy ORM, we want to reserve that for testing the equality (within the interpreter, non-topological) of Python objects. Sean _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
