Some answers below: On Dec 4, 2:20 pm, 43gm <[EMAIL PROTECTED]> wrote: > Talking with some python veterans (mainly SQLalchemists ;-), their > critique of web2py was summed in two words, "exec magic." In practical > terms, what does this mean... in terms of performance hits (at N > requests/sec), inefficient CPU / resource consumption, etc. ?
http://mdp.cti.depaul.edu/AlterEgo/default/show/131 > And ditto for MVC caching... http://groups.google.com/group/web2py/browse_thread/thread/cab9ef6e60e535e2 obviously results depend on the complexity of the page but bottle neck is always database access. > __ Thanks to Robin B for her insightful comments > > She mentioned: "making web2py more productive requires changes that > break backwards compatibility." Robin! Anything you want to correct? > The time for a major web2py revision could coincide with python 3.0 -- > Guido in http://bit.ly/py3kmentions a lot things which will break > anyways without code modifications. Also see his remarks re exec. none of the database drivers work with pyhton 3.0 because of the unicode issues. Once the respective authors port the drivers - and this will take long long time - it takes a week to make web2py work with 3.0 because it is already almost 100% compliant. It may break backward compatibility. Let's talk again about this next year. > Re critique: "Use WSGI middleware to customize applications (caching, routes, > exception handling)" > > Why did you choose web2py over pylons? You can use many wsgi plugins with web2py. we do not use any because the current implementation is cleaner and faster and bug free. Moreover in order to promise backward compatibility we cannot depend on third party packages. Compare the size of pylons with the size of web2py to achieve the same tasks. http://mdp.cti.depaul.edu/examples/static/web2py_dependency_graph.pdf Massimo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
