The difficulty stands in findind a proper way to do it (and changing web2py in order to support it being used as a proper package). The latest attempt was a real nightmare: a simple wrapper script was called to bootstrap a fresh directory from a tar(red) archive but it clearly wasn't (nor isn't) the right solution. Web2py is quite accustomed to be omnipotent in its own dir, and some of the "crucial" files are positioned in the root (logging.conf, routes.py, etc), and on top of that the applications/ folder is at the same level as gluon is. On top of that, the current repo holds the core code, contribs, apps, examples, scripts, etc, that are not "properly" pythonic. Some time ago I pushed some changes that would help running web2py with a different "root" folder (we always had a -f parameter, but it was never "stable" enough because of the aforementioned "conventions") and the core code can be used as a proper package...but that doesn't cover how (and when, and what, and etc) do the whole "set a new environment, prepare the scaffolding app, etc etc etc...
tl;dr: The first thing to cope with is absolutely the "design" of the solution. On Friday, July 29, 2016 at 4:09:57 PM UTC+2, Marlysson Silva wrote: > > It so much dificult? Or just incentive.. > > Em sexta-feira, 29 de julho de 2016 10:59:38 UTC-3, Massimo Di Pierro > escreveu: >> >> I will pay $200 if you help me put a version of web2py on PyPi. >> >> -- 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.
