The Python 1.6 License Explained

[Tim Peters]

I'm going to let CNRI defend themselves from now on <0.1 wink>.  One
clarification:

>>  9.So it supports proprietary ("closed source") use of Python too?
>>   Yes, provided you abide by the terms of the CNRI license and
>>   also include the CWI Copyright Notice and Permissions Statement.

[Pat McCann]
> "Proprietary" doesn't mean "closed source", I don't care how many times
> it's misused that way.  "Confidential" or "Trade Secret" might, but
> "closed source" should do the trick without waving around this FUDish
> bugaboo.  All copyrighted software is proprietary.

Don't blame CNRI for the questions:  those came from me, and I took them, in
almost all cases, verbatim from actual posts & email.  The questions got
edited into a state of emotional blandness before I saw this again, but the
"proprietary ('closed source')" is verbatim from what I compiled.
Rephrasing the questions to suit a particular agenda or hobbyhorse would
have made even the *questions* an exercise in political obfuscation.  Like
it or not, this is the question people actually asked, so that's the
question that was actually passed on.

just-hadda-get-that-off-my-chest-cuz-i-so-rarely-see-msgs-from-cnri-
    starting-"while-we-can't-speak-for-Tim-we're-pretty-sure-he-
    didn't-mean-to-be-a-jerk"<wink>-ly y'rs  - tim