Why?
The current web2py package that is available for installation via pip
installs glueon and other stuff to site-packages which is great for advance
usage, like importing Web2py stuff, for example, DAL functionality into
another Python application but this is not what someone checking out Web2py
would be expecting if they are looking for the familiar Web2py GUI and
contained webserver etc.
I put together a rough sketch of what a new pip package might setup for
people who want to try out (classic) Web2py via a pip installation. Helpful
input is appreciated.
As it is the draft should work from the terminal on most nix systems. Works
fine on OS X and should be fine on Ubuntu and others as well. Again,
feedback on layouts and so on and so forth would be great. It should not
"conflict" with the current bash installer in the Web2py/scripts directory
as it will install to ${HOME}/V_ENV/Web2py rather than ${HOME}/Web2py (on
nix systems), but I am not familiar with them all. Hopefully we can make it
OS agnostic as it can be "all Python" and it could serve as an example of
how to create and "anti-installer" for people who what to create os specific
installation packages for systems like debian and Windows and so on and so
forth.
http://www.web2pyslices.com/slices/take_slice/141
Let us know what you think.
Thanks,
Chris
--
Christopher Steel
Voice of Access
