Erik: > I've been thinking of cleaning up the main `sage` command anyways, > though it would be good to transition to a new, better UI for it as > well. > > For the top level of the `sage` command I wouldn't use Python. For > example, for things like `sage -sh` (or whatever the future equivalent > is) starting up the Python interpreter just to launch a shell is too > slow. But sub-command handling can still be implemented cleanly and > nicely in a bash script. Individual sub-commands may, in turn, be > written in Python depending on how relevant the overhead is.
It might be good to add some comments here: https://trac.sagemath.org/ticket/21 "command line option parsing" is the oldest opened Sage ticket! https://trac.sagemath.org/report/58?sort=ticket&asc=1&page=1 The second oldest is "notebook -- should be able export (=print) to latex/pdf/dvi", which could be finally closed when Jupyter notebook is the default notebook. -- William (http://wstein.org) -- 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.
