Going back to the original subject, I understand that a patch has been created and approved. What is the next step? Will this patch show up in the next file version of SAGE? Is there a schedule of such versions?
I realize that I could choose to recompile the source, but I am not in a position to do that. So I will wait until the fix gets incorporated into the distribution. When does that happen? Neal On Mar 7, 5:42 pm, Jason Grout <[EMAIL PROTECTED]> wrote: > Yi Qiang wrote: > > The problem is that the notebook is never launched to bound to a > > specific interface. Could you please file a trac# against this? > > > The specific issue is that in twistedconf.tac, we start the server like so: > > > strports.service('tls:8000:privateKey=/Users/yqiang/.sage/notebook/private.pem:certKey=/Users/yqiang/.sage/notebook/public.pem', > > factory) > > > It should read something like > > > strports.service('tls:8000:interface=127.0.0.1:privateKey=/Users/yqiang/.sage/notebook/private.pem:certKey=/Users/yqiang/.sage/notebook/public.pem', > > factory) > > > to only listen on localhost. > > > Someone more familiar with the notebook should probably write the patch, > > since the behavior of this should depend on what the user specifies when > > launching the notebook. > > > Cheers, > > Yi > > Yi and William, > > I just posted a patch up athttp://trac.sagemath.org/sage_trac/ticket/2423 > > Could one of you review it? It seems to solve the problem for me and > allows notebook(address=whatever) to work as expected as well. > > Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---