I don't know if this could be doable, but here is a proposal: to modify the tab completion code so that methods that consist only in raising a NotImplemented error are not shown.
This way we could keep the structure there for developpers to follow the name conventions, and we wouldn't confuse users with methods that are not implemented. On 4 ene, 15:47, Nathann Cohen <nathann.co...@gmail.com> wrote: > Helloooooooooooooo !!! > > Well, it provides a general interface for typical tasks (in order to avoid > > > that the same functionality is provided by methods of different names in > > different classes). I think it's useful, even though it means that some > > methods > > exist in a context in which they make no sense (and thus raise errors > > when they are called). > > > If you don't think that predefined method names are useful, then look at > > polynomials: > > I don't get your point at all. How can empty or not implemented method > "provide" anything ? I am totally free to define > t.LeADeEEIIiiing_CoeffICIENT() somewhere, even if some > t.leading_coefficient() method that raises an exception anyway exists > already. Why isn't "abs" defined in SageObject directly, then ? > > It creates a method where it has no meaning, and can only be used to raise > exceptions and confuse beginners. If there is a point to all that, I don't > get it.... O_o > > Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
