Would it make sense to have a subclass, or perhaps an option to ClonableArray.__init__, that determines whether or not to include the parent into the hash? The current behaviour seems rather error prone to me.
On the other hand, I am not sure whether GF(3)(4) == ZZ(4) is desirable. Martin On Friday, 9 December 2022 at 04:06:04 UTC+1 Travis Scrimshaw wrote: > Let me mostly rephrase what Nils said above with a bit more of specific > information. I would say this issue comes from a "feature" of > ClonableArray. The default hashing of ClonableArray is to also hash in the > parent and have elements in different parents not (by default) compare > equal. A coercion needs to get involved for "natural" equality (i.e., > ignoring the parent), which is a general issue within Sage. > > Best, > Travis > > > On Monday, December 5, 2022 at 6:03:53 PM UTC+9 Nils Bruin wrote: > >> On Sunday, 4 December 2022 at 23:45:00 UTC-8 j...@aims.ac.za wrote: >> >>> Note sage 9.2 (debian package) gives an error (sage 9.7 does not): >>> >>> >> Probably the following ticket then (Scrimshaw/Chapoton): >> >> https://trac.sagemath.org/ticket/15216 >> >> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/e06f0290-7851-48e6-91a5-4e5eeec53083n%40googlegroups.com.
