#6897: Migrate Notebook to Django
-------------------------+--------------------------------------------------
Reporter: timdumol | Owner: boothby
Type: enhancement | Status: new
Priority: major | Milestone: sage-feature
Component: notebook | Keywords:
Reviewer: | Author:
Merged: |
-------------------------+--------------------------------------------------
Description changed by timdumol:
Old description:
> Moving Notebook to Django will abstract the server and user
> authentication, and give us a free admin interface, as well as a large
> support codebase.
>
> 1On Aug 31, 11:20 pm, William Stein <[email protected]> wrote:
> > <SNIP>
> >
> > I'm not at all convinced that using twisted in any way (web or web2) is
> a
> > good idea for the Sage notebook. I plan to revisit this in late
> > September. The first thing I plan to do is consider switching from
> > twisted to Django, as is done in codenode -- seehttp://codenode.org/--
> > hopefully, even sharing code with that project. Of course, twisted
> could
> > still get used at a certain level behind the scenes, but the Sage
> notebook
> > would then no longer explicitly use it.
> >
> > So if you want to help as you describe above, perhaps you could
> accelerate
> > this. This involves:
> >
> > (1) getting familiar with Django, if you don't already know it.
> >
> > (2) reading through the current codenode codebase
> >
> > (3) then formulating a plan to replace server/notebook/twist.py with
> > something based either directly on Django, or possibly using codenode
> in
> > some way.
> >
> > The above is what I would do, but if you do it first that would be
> > spectacular.
> >
> > William
New description:
Moving Notebook to Django will abstract the server and user
authentication, and give us a free admin interface, as well as a large
support codebase.
Plan:
* Replace `guard.py` and `avatars.py` with Django user authentication.
* Replace `twist.py` with Django Views.
* Change `run_notebook.py` to launch Twisted as a WSGI container.
1On Aug 31, 11:20 pm, William Stein <[email protected]> wrote:
> <SNIP>
>
> I'm not at all convinced that using twisted in any way (web or web2) is
a
> good idea for the Sage notebook. I plan to revisit this in late
> September. The first thing I plan to do is consider switching from
> twisted to Django, as is done in codenode -- see http://codenode.org/--
> hopefully, even sharing code with that project. Of course, twisted
could
> still get used at a certain level behind the scenes, but the Sage
notebook
> would then no longer explicitly use it.
>
> So if you want to help as you describe above, perhaps you could
accelerate
> this. This involves:
>
> (1) getting familiar with Django, if you don't already know it.
>
> (2) reading through the current codenode codebase
>
> (3) then formulating a plan to replace server/notebook/twist.py with
> something based either directly on Django, or possibly using codenode in
> some way.
>
> The above is what I would do, but if you do it first that would be
> spectacular.
>
> William
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6897#comment:1>
Sage <http://sagemath.org/>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
