Which Python web framework is most like Ruby on Rails?

Paul Rubin http
Wed Dec 21 06:10:17 EST 2005


Richie Hindle <richie at entrian.com> writes:
> A good solution would be multiple-licensing.  You state that the
> code is (for example) triple-licensed under the GPL, LGPL and BSD
> licenses.  The user of your code decides which license to obey.
> It's no more work for you, and you can please almost everyone (the
> only people you won't please are those who believe that there is One
> True License, and frankly you should ignore them - it's your code).

That's silly, you might as well just use BSD instead of triple
licensing like that.  

> The only downside of allowing people to choose the BSD license
> rather than the GPL is that potentially someone can choose the BSD
> license, improve Karrigell, ship their product based on the improved
> code, and not give those improvements back to the community. 

Another downside to BSD is that it becomes impermissible to improve
Karrigell by transplanting GPL code into it from other programs.  Yet
another downside is that it leads some potential contributors to not
bother getting involved with such projects.  (On the other hand, it
possibly attracts some different potential contributors).

> But the Python license allows for this too, and Python hasn't
> suffered for it.

That Python hasn't suffered for it is a questionable assertion.

> IMO choosing a BSD license will get you more users than GPL, and
> the benefits of that will outweigh the potential downside.

Of course anyone is entitled to hold any opinion they choose.  I have
to say both notions expressed there (that BSD will attract more users,
and that merely attracting more users produces such big benefits) are
questionable.  As for me, for something like this, I'd be more
interested in attracting more contributors than in merely attracting
more users with me doing all the work.  But what Karrigell's author
wants is of course purely up to the him.



More information about the Python-list mailing list