On 11/6/2010 4:46 PM, mdipierro wrote:
What can I say? They managed to break backward compatibility for 3 frameworks at once. Users will be pissed.
While I agree that backward compatibility is *very* comforting to users, I see a few possible problems with being completely unforgiving about the matter:
* Python 3.X++, there are likely to be reasons or requirements that things be changed to continue using web2py with the most recent releases of Python. * Paradigm shifts in technology, "Web3", or newer WSGIs, or some other basic component making a quantum leap that just works differently. * An attempt to merge web2py with a compatible framework would be unfriendly if we say they must change many things, but we will change nothing.
-- Andrew Thompson http://aktzero.com/
