On Mon, Mar 16, 2015 at 10:41 PM, Shannon Cruey < [email protected]> wrote:
> [...] > I'd suggest a fork, then a slash and burn back to the core of web.py. > Same simple foundation, with critical features included (db and sessions), > and a well defined plugin framework for adding things like the > aforementioned beaker, jinja, etc. It'd probably be easy enough to make > the fork Py2.7+, as dropping Py2.6 and older gets rid of a huge chunk of > the blockers for 3.0 compatibility. > +1 I think branching off python2 and continue with the development on master might be even better. > > It's hard to shore up the documentation of an older, full featured > project. Forking and stripping it down makes new documentation much > easier, especially when that documentation comes in the form of > downloadable, working prototypes as mentioned. > I think we should go with Sphinx based documentation. Anand -- You received this message because you are subscribed to the Google Groups "web.py" 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/webpy. For more options, visit https://groups.google.com/d/optout.
