the web2py files gluon/*.py are compiled as you would expect and are in gluon/*.pyc but, unlike flask or django where the user code imports the framework, in web2py it is the framework that executes the user code (this allows running multiple apps under one web2py). When web2py executes the models&controllers, it compiles them and caches the compiled versions in memory. Because of this design, if a file changes, it recompiles them on the fly even when running under nginx. If your app imports any modules in site-packages or app/modules/ they produce *.pyc files as you would expect.
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
