http://groups.google.com/group/pl.comp.lang.python/browse_thread/
thread/7a6e1b5a52c4766f/923f2acb0b5762a3?#923f2acb0b5762a3
If you speak polish, could you help get things straight?
1) web2py is GPL2 but this does not extend to apps developed with
web2py unless they include web2py code. Apps are not derivative
applications. Example: the BSD operarive system is compiled with gcc
which is GPL but BSD is not GPL.
http://mdp.cti.depaul.edu/AlterEgo/default/show/47
2) web2py works with memcache, it is just that there is not much
reason to.
web2py is GPLv2 with one exception: you can redistribute my binaries
with your applications (you can charge for your apps but not for the
binaries)
According to the GPLv2 any derivative works (i.e. programs that
include web2py source code) must be released under GPLv2.
The point I make the GPL does not extend to modules, programs, etc.
that require web2py but that do not include web2py source code
because they are not "derivative work".
That means that as long as you do not copy code from the gluon folder
into your applications (and why would you anyway?) and you make clear
to your clients where you app ends and web2py starts, you are not
bound to the GPL.
If this is still not clear think of this: you use Linux (which is
GPL) to develop a Linux application that you release in closed
source. That is fine - you can do it - because the application
requires linux but it is not derivative work and does not include
Linux source code. (There may be issue with static linking libraries
but that is not the case with python and web2py).
I actually encourage you to distribute your code under other licenses
including closed source ones. Most of the appliances I developed for
web2py are in fact released under MIT, BSD or even public domain.
Others I charge for.
This is all spelled out in the license.
I believe this is best possible situation for developers.
Massimo