Yoooooooooooooo, About your order of preferences:
> 1) fix and merge #19016 before the stable +1, but given the amount of work I do not see it happen quickly enough. > 2) merge #19321 and #19331 before the stable Big +1 to that. With [new individual hash functions] added to [a default hash to 0] the code would 1) be correct and 2) some hash would already be fixed. To me, we could also add with the default 0 hash a message saying: "An update to the __hash__ function of Element may make your code slower than usual. This was necessary to avoid a ganerous behaviour, and will be fixed in the next release" > 3) merge #19321 and #19302 before the stable [subtitle: this is the same as 2), only with a stopgap and no default hash] -- the users would know that there is a bug (and worry), but at least they would know it. It is ranked 3, as it should. > 4) merge #19321 and #19302 in the first beta The users get no warning, we hide it from them. Definitely number 4. All in all, I second this ranking. Nathann -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
