FOR APPROVAL - Python License Changes

Wilson, Andrew andrew.wilson at
Thu May 26 22:51:44 UTC 2011

John Cowan wrote:

> From what I understand, only the top-level license is operative.  Other
> licenses are there because their own conditions say they must be carried
> along with derivatives of the old code, but all old code has acquired
> enough patches that it is no longer available solely on the terms of old
> licenses.

Pardon me if this is an obvious question, but couldn't CNRI address this
by saying, as licensor, that all its pre-2.1 licensed code may now be distributed
under 2.1? {The way Regents of UC Berkeley declared all of their 4-clause
licensed code in the field could be distributed under 3-clause BSD.}
Doesn't solve the problem of non-CNRI patches, but at least takes
a stab at de-cluttering Python licensing.

May I also suggest that Python 2.1 should carry a clause explicitly stating
the license may be updated by the license steward (EPL as the
model here).

Andy Wilson
Intel open source technology center

More information about the License-review mailing list