summaryrefslogtreecommitdiff
path: root/LICENSE
Commit message (Collapse)AuthorAgeFilesLines
* [2.7] advance copyright years to 2018 (GH-5094). (#5105)Benjamin Peterson2018-01-041-3/+3
| | | (cherry picked from commit 65f2a6dcc2bc28a8566b74c8e9273f982331ec48)
* bpo-25910: Update LICENSE (GH-2873) (GH-2969)Mariatta2017-07-311-6/+5
| | | | Use the copy provided in https://bugs.python.org/issue25910GH-msg295200 (cherry picked from commit 8474d87165593bac2bc231287f42c4cff3fd6aaf)
* ring in 2017 for PythonBenjamin Peterson2017-01-011-1/+1
|
* reflowBenjamin Peterson2016-01-011-2/+3
|
* 2016 will be another year of writing copyrighted codeBenjamin Peterson2016-01-011-1/+1
|
* update for copyright for 2015Benjamin Peterson2014-12-311-2/+2
|
* update copyright yearBenjamin Peterson2013-12-311-1/+1
|
* Closes #19043: remove detailed listing of versions from license filesGeorg Brandl2013-09-221-26/+1
| | | | | | Since all versions since 2.2 are under the same licensing terms, this saves the release manager from touching the two files for every new minor release.
* bring Python into 2013Benjamin Peterson2012-12-311-2/+2
|
* add another year to glorious PSF IPBenjamin Peterson2011-12-311-3/+3
|
* add 2.7 to the license listBenjamin Peterson2010-07-031-0/+1
|
* Add 2.6.5.Georg Brandl2010-04-021-0/+1
|
* update copyright yearBenjamin Peterson2010-01-011-3/+3
|
* add 2.6.x point releasesBenjamin Peterson2009-12-131-0/+3
|
* welcome to 2009, Python!Benjamin Peterson2009-01-011-9/+8
|
* add some recent releases to the listBenjamin Peterson2008-12-201-0/+3
|
* More copyright year and version number bumpsv2.6a1Barry Warsaw2008-03-011-1/+2
|
* Some new year updates.Georg Brandl2007-04-241-0/+2
|
* update to (c) years to include 2007Anthony Baxter2007-01-061-3/+3
|
* preparation for 2.5a1Anthony Baxter2006-04-031-0/+2
|
* Update general copyright years to 2006.Georg Brandl2006-02-111-1/+1
|
* Add 2.4.2 to LICENSE.Georg Brandl2005-10-211-0/+1
|
* merge from branchesAnthony Baxter2005-03-101-3/+5
|
* In paragraph 1, changedTim Peters2004-10-261-2/+2
| | | | | | Python software to this software ("Python")
* Converted some stinking hard tabs. Left the fragrant hard tabs alone.Tim Peters2004-10-231-1/+1
|
* Move to version 2 of the PSF license, approved by the Board earlier today.Tim Peters2004-10-231-12/+12
|
* license updates for 2.4 (cleared with tim, on behalf of the psf)Anthony Baxter2004-07-081-11/+12
|
* Added 2.3.3 and 2.3.4 to the release table. Added 2004 to the list ofTim Peters2004-05-111-3/+5
| | | | copyright years.
* added 2.3.2Anthony Baxter2003-09-301-0/+1
|
* include 2.3.1Anthony Baxter2003-09-231-0/+1
|
* Add historical note for Python 2.2.3Barry Warsaw2003-05-221-0/+1
|
* Update the copyright year.Guido van Rossum2003-01-021-1/+1
|
* Various updates to the version number, on the eve of the 2.3a1 release.Guido van Rossum2002-12-311-11/+12
|
* Update info for impending 2.2.2.Tim Peters2002-10-061-0/+1
|
* At CNRI's request, I'm changing the status of 1.6.1 fromGuido van Rossum2002-04-111-1/+6
| | | | | | not-GPL-compatible to GPL-compatible, with a footnote explaining that RMS disagrees. I'm not going to discuss this further -- both sides (CNRI and RMS) will argue their POV till they're blue in the face.
* Update table of releases.Tim Peters2002-04-081-0/+3
|
* Removed old Digital Creations copyright/license notices (withGuido van Rossum2002-04-041-5/+6
| | | | | permission from Paul Everitt). Also removed a few other references to Digital Creations and changed the remaining ones to Zope Corporation.
* Add 2002 to PSF copyrights.Michael W. Hudson2002-02-271-2/+3
| | | | | Doc/README is odd; it assigns some copyright to the PSF in 2000, when I didn't think it existed...
* A new attempt at rationalizing the "history of the software" section,Guido van Rossum2001-07-171-45/+60
| | | | | | with a table clarifying which releases are GPL-compatible. Also unified the headings for the various licenses.
* Note that 2.0.1 is also a PSF release. (Gregor Hoffleit, SF #433223.)Guido van Rossum2001-06-141-5/+4
|
* Make the license GPL-compatible.Guido van Rossum2001-05-041-16/+5
|
* Tim convinced me to augment the PSF license with a final clause justGuido van Rossum2001-04-131-0/+4
| | | | | like the one in the BeOpen license (and similar to the one in the CNRI license, but with the "click-to-accept" part elided).
* Oops. Need an extra blank line after the PSF license.Guido van Rossum2001-04-131-0/+1
|
* - Inserted the (tentative) PSF license.Guido van Rossum2001-04-131-9/+64
| | | | | | | | - Removed the subsection numbering in section B (each time a new license is inserted in the front, the others have to be renumbered). - Changed the words in the intro to avoid implying that 1.6.1 is GPL-compatible.
* Correct the header over the string of licenses -- it's "PYTHON", notGuido van Rossum2001-04-101-2/+2
| | | | "Python 1.6.1".
* Fix typo in history.Thomas Wouters2001-03-221-1/+1
|
* Updated history. Incorporated 1.6.1 license.Guido van Rossum2001-03-221-67/+76
|
* Add note about copyright ownership and license situation.Guido van Rossum2001-01-181-0/+10
|
* Typo detected by "the miraculous Debian package lint tool "lintian"Guido van Rossum2000-12-121-1/+1
| | | | | | | (http://package.debian.org/lintian), which includes a spellchecker for common typos in control files of packages... You see, we're so paranoid that we even have automatic tools that keep monitoring license files ;-)" (Gregor Hoffleit)
* Place the full text of the CNRI license verbatim in the LICENSE file.Guido van Rossum2000-10-101-5/+67
| | | | Who know where the handle will point to tomorrow?