Thanks for the great post, Timothy. You've made me feel good about my decision to use web2py!!
I can't believe that CherryPy and FormEncode would break backward- compatibility after only a minor version number change. That's not acceptable for a library. I mean look at Python. It has a million cludgy hacks in it at this point, but these are necessary to maintain compatibility until the next major revision. And in fact, the next major revision will come with an automatic transfer script that will fix your old code. Following Python's example would be my suggestion for web2py over the long term. This way web2py can change it's API on rare occasions, and still claim that it will never break backward-compatibility. ;) And Massimo: thanks for that awesome cache speedup on GAE, I will really appreciate that when my site goes public. :-D --Jonathan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
