I think the following is also a source of frustration: v=vector([1,2,3]) rm=matrix(v)#This will be a row matrix cm=v.transpose()#This will be a column matrix.
What would the convention be for this one? This came up in another discussion: http://groups.google.com/group/sage-support/browse_thread/thread/24fa62276520b799/2ba996a4f9d18545?hl=en&lnk=gst&q=vector+to+matrix#2ba996a4f9d18545 Keep the good work. On Dec 14, 3:48 am, mabshoff <michael.absh...@mathematik.uni- dortmund.de> wrote: > On Dec 14, 2:44 am, daveloeffler <dave.loeff...@gmail.com> wrote: > > > > > That > > > On Dec 13, 6:50 pm, Jason Grout <jason-s...@creativetrax.com> wrote: > > > > That sounds the best way. We'll make kernel_left/right (along with > > > left/right_kernel) the global functions, and people can do > > > > kernel = left_kernel > > > > in their init.sage or at the beginning of their session, if they want. > > > \begin{devils-advocate} > > That's inviting people to write code which will then silently and > > mysteriously not work as soon as they pass it on to someone else. > > \end{devils-advocate} > > > David > > Yes, people will do dumb things if they are given a chance, but at > least it will not be code in the Sage library that causes any more > trouble. I guess someone has to get burned a couple times to realize > that customization can be evil. If this happens a lot it won't be long > before we ask bug submitters to provide their init.sage along with the > code in question that causes trouble. > > Cheers, > > Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
