Hi, > What's the problem with raising a NotImplementedError for a method > that is not implemented?
I don't have a problem with that, but I tent to prefer not to have methods available (see below) which are not implemented anyway. > Why should one want that these methods are > "deactivated"? What shall "deactivated" actually mean? That they don't > appear in introspection? By "deactivated", I mean that this method doesn't appear as a usable method for the user. I feel like the tab completion is often so long, that it is quite hard to find some method. So why not removing all methods from this list which I cannot use anyway? I think it is also annoying to find and try to use some method which then only raises an error. Best, Christian -- 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-devel@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.