Re: New License/Exception Request: Python Imaging Library License

J Lovejoy

Hi Mark, Philippe,

I just had a closer look at this using Alan’s handy License Diff tool, which gave it a close match to MIT-CMU - the only difference between this license and MIT-CMU is:
- “and its associated documentation” instead of just “and its documentation” in the first sentence (Permission to use…)
- use of the Oxford comma: “use, copy, modify, and distribute”
- a comma added after “copies”, as in: “provided that the above copyright notice appears in all copies, and that both…”
- a comma after “specific” in last line, as in: “ pertaining to distraction of the software without specific, written…”
- “prior permission” instead of “permission” in last sentence of first paragraph.

I can also see (by just doing a naked-eye analysis) how this might also match to a variation of the HPND.

What do the other lawyers think though about the difference between this and MIT-CMU? Are these slight variations something we might simply capture with markup and then this license would be a valid match to MIT-CMU?

I made a new issue in Github repo to track here:


On Dec 14, 2018, at 1:28 AM, Philippe Ombredanne <pombredanne@...> wrote:

Hi Mark:

On Thu, Dec 13, 2018 at 8:42 PM Mark Atwood via Lists.Spdx.Org
<> wrote:
Provide a proposed Full Name for the license or exception.
Python Imaging Library License
It looks to me as a proper historical permission (HPND )
This has been detected by the ScanCode toolkit as an HPND alright and
this is within the "matching guidelines" too IMHO...
unless this additional "prefix" is considered as creating something
entirely new:
"By obtaining, using, and/or copying this software and/or its associated
documentation, you agree that you have read, understood, and will comply with
the following terms and conditions:" ...

Philippe Ombredanne

+1 650 799 0949 | pombredanne@...
DejaCode - What's in your code?! -
AboutCode - Open source for open source -
nexB Inc. -

Join { to automatically receive all group messages.