Saturday, April 01, 2006

Python 2.5 Licensing Change

[To avoid any uncertainty on the part of later readers, this article was part of an April Fool's joke. No such licensing changes are currently anticipated. SH]

April 1, 2006 -- The Python Software Foundation today announces a significant change to the licensing conditions for the Python programming language. Since this change will require payments by commercial users this article explains the reasoning that led the Board to the decision to change Python's licensing terms and conditions. First, the details of the change: Section B, clause 2 is modified to read (our italics):
2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 2.5 alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright (c) 2001-2006 Python Software Foundation; All Rights Reserved" are retained in Python 2.5 alone or in any derivative version prepared by Licensee. License is royalty free for applications and derivative products distributed under any approved open source license. Other applications and derivative products are required to pay the Python Software Foundation a royalty of $US 1.25 per installed copy.
The Board realises that this change will be contentious. There are many advantages to making it, however, which we feel will benefit the Python community at large and the PSF membership in particular. Users who wish to make commercial use of Python on a royalty-free basis are encouraged to continue using Python 2.4, whose licensing conditions remain the same. The decision has been borne of necessity: the Foundation is supposed to promote the advance of the Python language, but to do this properly would involve many expenses that the Foundation simply cannot afford to incur without increasing its income. The additional money will be put to good use, funding several adventurous programs:
  • We anticipate being able to pay individuals to speak about Python to encourage the growth of the user community; this will in turn increase revenues still further.
  • The treasurer's projections indicate that by the year 2010 we should be able to make PyCon a completely free conference.
  • A further round of grants will be awarded for the development of new language features, including a) making strings mutable; b) re-implementing regular expressions to give better conformance with Perl; and c) porting Python to the simple CPU.
Python has always been a community-based language, and the Board of the Foundation sincerely hope that users will send us their own ideas for taking advantage of the significant funding that this change is likely to provide. The Board is grateful to the Advanced Program for Research In Licensing, whose First Object-Oriented License was a model for these changes. Interested readers can find out more about this license on this page.

18 comments:

xtian said...

I think this is a briliant idea! The Python developers can use the extra revenue generated to make sorely needed improvements to the language, including finally adding the static typing that Guido didn't understand when the first versions of the language were created, and adding in the braces that were forgotten.

Ideally, some additional changes to finally enable enterprise development in Python will be made: the lack of checked exceptions means that the language simply isn't safe to be used in a commercial context as it is.

Doug said...

Perhaps you can get the BSA to help you enforce this? Why not just urge developers to use Perl or Ruby and avoid the beauraucratic hassle.

Anonymous said...

Yeah, dealing with that Beau guy is a real hassle.

DougN said...

YEA! Now all those silly derivitive web frameworks and Redhat Server installs can fork over some serious cash!!! And those pesky string, good to hear I can modify all my stings which are == "April" and turn them into "Fools" globally.

Anonymous said...

Argh! Not funny! =/...

Anonymous said...

Is this license change related to Guido quitting as BDFL? I was just looking at the SQL On Rails site and there is a quote to that effect attributed to Guido.

If we need a new BDFL, I nominate Steve Holden.

Tim Peters said...

It figures that Steve "Holier Than Thou" Holden voted against this change. Don't think you can't be voted off the PSF Board, limey! The inflow of cash will enable vital changes, like changing __main__ to ___main___, and finally getting rid of unittest and doctest.

Anonymous said...

Doug said:
"Perhaps you can get the BSA to help you enforce this?"

But in fact, python has the perfect enforcement group in the form of the PSU. In fact, they've already werbgw4
525hwrt-
w
yny

EP said...

Well, great. This shuts down my project at work. Even though I am using 2.4, our IT management simply is not going to allow us to develop an application in a language with licensing terms like this. The buck per user is nothing; we'd have to spend 200K putting in auditable systems to track usage and staff to prove our compliance.

It was hard enough when I first brought up Python and its BDFL with my IT Director - he was unfamiliar with the language, kept saying "what's wrong with Perl?", and highly suspicious (his words) "of any language controlled by a single person named 'Guido'".

In fact, he kept asking "What does Larry think about all this?"

And now he will be convinced Guido is infact part of organized crime (whether or not that crime is legal).

Steve, thanks for fighting the good fight - do you want to jump ship and help a small group of us develop a new language? We're still in the process of naming it, but right now are calling it Xah (catchy, eh?) Its cute like Python used to be... for instance, instead of throwing exceptions it just complains...

EP

GerdusVZ said...

arg, i can't believe i didn't look at the date! Almost gave me a heart attack.

Jack Diederich said...

My mind boggles. Doug, how the heck are the Boy Scouts of America going to help in enforcing this? Sure, a couple troops with .22s could take Paris in an afternoon, but licensing enforcement?

Anonymous said...

dude, this intended joke is not indented very well.

Anonymous said...

At least it would match the Qt license...

Anonymous said...

The perfect way to stop the growth of the Python community. I think it is a bad idea.

Anonymous said...

That was mean !

Anonymous said...

You'll kill python...
This is the Micro$oft way...

Anonymous said...

Please, be carefull with April 1 fool's day. Many people outside the USA read the news but have not idea what April 1 means. Can be dangerous!.

I urge an unicode/I18n fool's day.

Anonymous said...

I woke up this morning with a feeling this must be an April fool thing and, honestly, I was *relieved* when I saw that was it. I got caught last year with a similarly frightening joke from the postgresql team that were saying they were abandoning C in favor of Java. Scared the snot out of me. Please, don't do this too often ;-).