hi As my experience with web2py grows I find an increased need to make it work in 2 main environments/behaviors.
The first mode would be "development" and it should run with smaller buffers, extra debug features/output, auto-refresh for files like routes.py so that you can edit routes on-the-fly, no caching mechanisms that can trick the programmers and it could even be a testing mode for new web2py features. Then there would be "production" mode, meant to be simple, stable and as fast as possible. Thinking about it, doesn't make sense that such different usages run the same way. This idea doesn't break the convention over configuration philosophy used in web2py. Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
