What would it take to get the flask notebook into 4.7? If that is
absolutely not possible, what would it take to get it into the release
after 4.7?
William's class and others have been testing flask.sagenb.org. I think
we've taken care of every problem that has come up, with the possible
exception of http://code.google.com/p/sagenb/issues/detail?id=4 (I
incorporated what may be a fix into my sagenb tree on googlecode, but
it's hard to diagnose since I've only seen it on flask.sagenb.org, not
my local notebook).
It seems like at least this should happen:
1. Rado reviews and pulls my latest bugfixes/changes that address
several bugs.
2. Rado commits his fix for data URLs
3. William pulls the new codebase from Rado and updates flask.sagenb.org
so people can test the latest version of the code.
What is the ETA for 4.7? We're at alpha5 now, so it's probably not too
long...
Thanks,
Jason
--
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
URL: http://www.sagemath.org
