>> I do not know much about the poset package, but I also had a lot >> of trouble last spring with various comparison functions overwriting >> each other (in a not very consistent fashion) when writing code >> for crystals. I remember spending a whole day with Nicolas on this. >> >> Here is a reference: >> >> http://www.python.org/doc/2.4.4/ref/customization.html >> >> But it would be a good idea to have clean conventions of which >> methods need to be implemented etc.. Right now things do not >> seem very consistent in sage. > > You are right ! The main problem here is not only a question of convention but > also a problem of very bad side effect in Posets:
I think the general conventions for comparisons in sage should be discussed (perhaps even on sage-devel??) since as I said this has popped up in quite a few places and should be fixed! Cheers, Anne -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-de...@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.