Earing money with Python software (was: More on Protecting Source Code)

[Terry Reedy]

"Richie Hindle" <richie at entrian.com> wrote in message
news:8a6ba1da.0209180206.2d47f2bd at posting.google.com...
> For library code (and tools like bridgekeeper which have a library
> component), my approach is to release a single version under two
> licenses, one free (as in both speech and beer) for use in Open
Source
> projects and one with a fee for use in closed source projects.

Perhaps we should call this a Chameleon license: the software takes on
the 'color' of its use-environment.

TJR