> It seems to me that as a general principle, a method whose name is an > abbreviation of the name of another method should actually be the same > method. Anything else is hugely confusing to a user. Both the > functionalities described are, of course, useful, but giving them such > similar names has a times certainly confused me.
+1 In order to keep the two features, however, what would you think of a solution with coeffs, coefficients_list and coefficients_dict ? It does not look very clean, but that is the only way I see to make it clearer while not removing the abbreviation. This would require a deprecation for "coefficients", though. Alternative solution: it is possible to make coeffs an alias to coefficients, and to give them both the two features. coeffs(dense=True) == coefficients(dense=True) coeffs(sparse=True) == coefficients(sparse=True) This would require to pick a default value for sparse/dense, which also means that one of the two functions will have to display a deprecation warning for a while. 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.
