On 2014-11-06 02:41, kcrisman wrote: > > It is an interface that worked the same way for a long time and > achieved > de facto status. > > > Fine, if you don't want a way to start the ipython notebook then I can > take > out the optional argument. > > > Perhaps I will leave it to those who use this feature to comment next.
As you somehow ask me as the one who started this discussion to comment again, I try summarize my opinion on that issue. I and my co-authors used that feature (-n directory=sage.sagenb) for years now in order to keep our sage worksheets associated to a paper under the same version control as the paper itself. When sage-6.4.beta6 came out, I was not able to quickly find out the problem, because the problem was twofold (I'd have had to add "default" or "sagenb" and fix the quotes issue). Since that time, we adapted different strategies, partly starting the notebook inside sage, partly manually converting our worksheets to the ipython notebook. The quotes issue is now fixed in the trac ticket mentioned somewhere in this thread. On the long run, IMHO, - having -n with an optional argument is the correct solution, - requiring separation of the non-options by "--" is also the correct solution, - I always found these key=value pairs on the command line as something strange. I currently do not yet have access to a compiled version of 6.4.rc1; therefore, I do not know - whether the option --notebook-dir introduced for -n ipython still works or has been removed due to the change in the default notebook directory. IMHO it should still be there; - whether the option --notebook-dir works with sagenb; IMHO it should; - whether the option --notebook-dir is documented in ./sage -h (or --advanced); IMHO it should be - on whether the old behaviour "-n directory=sage.sagenb" is documented somewhere and whether this documentation has been adapted to the new situation. I'd appreciate moving more of the key=value command line arguments to proper command line options, e.g. --notebook-port=..., usable in all notebooks. I do not know whether users running into the error message Volker quoted will be able to react appropriately. To summarize: I am not happy with the change in the interface without deprecation of the old behaviour, but if writing a work-around is too complicated, then let's keep it that way and hope that users using this old behaviour will either adapt their scripts or move to ipynb. Kind regards, CH -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
