Reading through the code base, it seems switching to Django will entail replacing the user authentication system with Django's -- or at least it seems the cleanest way to do it. Django views can be relatively easily implemented by just translating the code in `twist.py`. The authentication seems to pose the largest obstacle.
I've made a new ticket regarding this: http://trac.sagemath.org/sage_trac/ticket/6897 On Aug 31, 11:20 pm, William Stein <wst...@gmail.com> 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 --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
