On Thursday, October 27, 2016 at 2:42:56 PM UTC-7, Travis Scrimshaw wrote: > > > > On Thursday, October 27, 2016 at 2:12:01 PM UTC-5, William wrote: >> >> On Thu, Oct 27, 2016 at 11:25 AM, kcrisman <kcri...@gmail.com> wrote: >> > >> > >> > On Thursday, October 27, 2016 at 2:11:58 PM UTC-4, John H Palmieri >> wrote: >> >> >> >> (1) Why should a nonsquare matrix even have an "is_similar" method? >> Can we >> >> get rid of that? (Same for "determinant" and some other methods.) >> > >> > >> > Those are not even the most annoying methods like this throughout Sage >> that >> > are not actually implemented but nonetheless appear in tab-completion, >> > thanks for the reminder - not sure how to fix it without putting in a >> bunch >> > of super-classes that don't have them. >> >> We could change how tab completion works to have a hook/way to exclude >> a list of methods. That's a simple backward compatible fix that does >> not require any new classes, and can be iteratively applied with 0 >> change in efficiency. >> >> The OOP way would be to have a mix-in class and subclasses for square > matrices that implement these methods. This would mean setting the Element > attribute in the initialization of the parent, but that's not so bad IMO. > This would be my fix; it just takes a bit more work. >
Or plug (square) matrices into the category framework? Would that be too slow? I see that there is a file categories/matrix_algebras.py, but there is not much in it. -- John -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
