-1 for breaking compatibility. I can see the need here and there, but I have some apps running on web2py, and thinking that I'll have to make sure they work aain, just because we got to a rounded number - is unthinkable. When web2py moves to python 3 - it'll make sense to reexamine all features. But for now - leave it backword compatible. OH, and +1 for the docs. But that has nothing to do with the version, but has more with creating a policy about new features (like, no commit without a document of a feature, including example). Some policy should be applied to doctests too.
On Sep 21, 6:16 am, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote: > we'll work on it. > > On Sep 20, 6:49 pm, niknok <nikolai...@gmail.com> wrote: > > > > > > > > > Web2Py 2.0 must be *fully* documented in online book. > > > On Sep 20, 4:26 pm, Mengu <whalb...@gmail.com> wrote: > > > > anything special coming up? > > > > will it broke backward compatibility? nobody needs backward > > > compatibility in a major version. > > > > are there any plans for a clean up?
