> I think that the rule of thumb ("if you want to implement a magical
> python method __bla__ in Sage, then you should check whether a default
> implementation exists, in which case you usually have to implement
> _bla_, and the documentation of the default __bla__ gives you more
> details what you can assume for _bla_") is way better than chosing names
> such as _bla_which_is_to_be_used_in_this_particular_context_.It is better only when you know the convention. And if you don't, then you will fight with bugs you do not understand until you: 1) learn it 2) give up, thinking that Sage's design is awful You need to have a good doc, but the doc does not do everything. Sometimes you do not know that some doc solves the problem you have, nor when to find it. Making these names clearer would have helped me. The point now, is that if you don't take the advice of newcomers about this, you will never see the problem again. Because now, I also know the convention and so I will never complain about this again. I will know it, no problem for me. But *MANY* times I tried to mess with categories, and every single time I gave up saying that this thing was a mess. And you have no idea how many people followed the same path before. I don't have any idea about this either. But there are things that developpers see, and other that newcomers see. Nathann -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/d/optout.
