ThomasV
4 years ago
committed by
GitHub
5 changed files with 631 additions and 1 deletions
@ -0,0 +1,279 @@ |
|||||||
|
A. HISTORY OF THE SOFTWARE |
||||||
|
========================== |
||||||
|
|
||||||
|
Python was created in the early 1990s by Guido van Rossum at Stichting |
||||||
|
Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands |
||||||
|
as a successor of a language called ABC. Guido remains Python's |
||||||
|
principal author, although it includes many contributions from others. |
||||||
|
|
||||||
|
In 1995, Guido continued his work on Python at the Corporation for |
||||||
|
National Research Initiatives (CNRI, see http://www.cnri.reston.va.us) |
||||||
|
in Reston, Virginia where he released several versions of the |
||||||
|
software. |
||||||
|
|
||||||
|
In May 2000, Guido and the Python core development team moved to |
||||||
|
BeOpen.com to form the BeOpen PythonLabs team. In October of the same |
||||||
|
year, the PythonLabs team moved to Digital Creations, which became |
||||||
|
Zope Corporation. In 2001, the Python Software Foundation (PSF, see |
||||||
|
https://www.python.org/psf/) was formed, a non-profit organization |
||||||
|
created specifically to own Python-related Intellectual Property. |
||||||
|
Zope Corporation was a sponsoring member of the PSF. |
||||||
|
|
||||||
|
All Python releases are Open Source (see http://www.opensource.org for |
||||||
|
the Open Source Definition). Historically, most, but not all, Python |
||||||
|
releases have also been GPL-compatible; the table below summarizes |
||||||
|
the various releases. |
||||||
|
|
||||||
|
Release Derived Year Owner GPL- |
||||||
|
from compatible? (1) |
||||||
|
|
||||||
|
0.9.0 thru 1.2 1991-1995 CWI yes |
||||||
|
1.3 thru 1.5.2 1.2 1995-1999 CNRI yes |
||||||
|
1.6 1.5.2 2000 CNRI no |
||||||
|
2.0 1.6 2000 BeOpen.com no |
||||||
|
1.6.1 1.6 2001 CNRI yes (2) |
||||||
|
2.1 2.0+1.6.1 2001 PSF no |
||||||
|
2.0.1 2.0+1.6.1 2001 PSF yes |
||||||
|
2.1.1 2.1+2.0.1 2001 PSF yes |
||||||
|
2.1.2 2.1.1 2002 PSF yes |
||||||
|
2.1.3 2.1.2 2002 PSF yes |
||||||
|
2.2 and above 2.1.1 2001-now PSF yes |
||||||
|
|
||||||
|
Footnotes: |
||||||
|
|
||||||
|
(1) GPL-compatible doesn't mean that we're distributing Python under |
||||||
|
the GPL. All Python licenses, unlike the GPL, let you distribute |
||||||
|
a modified version without making your changes open source. The |
||||||
|
GPL-compatible licenses make it possible to combine Python with |
||||||
|
other software that is released under the GPL; the others don't. |
||||||
|
|
||||||
|
(2) According to Richard Stallman, 1.6.1 is not GPL-compatible, |
||||||
|
because its license has a choice of law clause. According to |
||||||
|
CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1 |
||||||
|
is "not incompatible" with the GPL. |
||||||
|
|
||||||
|
Thanks to the many outside volunteers who have worked under Guido's |
||||||
|
direction to make these releases possible. |
||||||
|
|
||||||
|
|
||||||
|
B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON |
||||||
|
=============================================================== |
||||||
|
|
||||||
|
Python software and documentation are licensed under the |
||||||
|
Python Software Foundation License Version 2. |
||||||
|
|
||||||
|
Starting with Python 3.8.6, examples, recipes, and other code in |
||||||
|
the documentation are dual licensed under the PSF License Version 2 |
||||||
|
and the Zero-Clause BSD license. |
||||||
|
|
||||||
|
Some software incorporated into Python is under different licenses. |
||||||
|
The licenses are listed with code falling under that license. |
||||||
|
|
||||||
|
|
||||||
|
PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 |
||||||
|
-------------------------------------------- |
||||||
|
|
||||||
|
1. This LICENSE AGREEMENT is between the Python Software Foundation |
||||||
|
("PSF"), and the Individual or Organization ("Licensee") accessing and |
||||||
|
otherwise using this software ("Python") in source or binary form and |
||||||
|
its associated documentation. |
||||||
|
|
||||||
|
2. Subject to the terms and conditions of this License Agreement, PSF hereby |
||||||
|
grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, |
||||||
|
analyze, test, perform and/or display publicly, prepare derivative works, |
||||||
|
distribute, and otherwise use Python alone or in any derivative version, |
||||||
|
provided, however, that PSF's License Agreement and PSF's notice of copyright, |
||||||
|
i.e., "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, |
||||||
|
2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022 Python Software Foundation; |
||||||
|
All Rights Reserved" are retained in Python alone or in any derivative version |
||||||
|
prepared by Licensee. |
||||||
|
|
||||||
|
3. In the event Licensee prepares a derivative work that is based on |
||||||
|
or incorporates Python or any part thereof, and wants to make |
||||||
|
the derivative work available to others as provided herein, then |
||||||
|
Licensee hereby agrees to include in any such work a brief summary of |
||||||
|
the changes made to Python. |
||||||
|
|
||||||
|
4. PSF is making Python available to Licensee on an "AS IS" |
||||||
|
basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR |
||||||
|
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND |
||||||
|
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS |
||||||
|
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT |
||||||
|
INFRINGE ANY THIRD PARTY RIGHTS. |
||||||
|
|
||||||
|
5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON |
||||||
|
FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS |
||||||
|
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, |
||||||
|
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. |
||||||
|
|
||||||
|
6. This License Agreement will automatically terminate upon a material |
||||||
|
breach of its terms and conditions. |
||||||
|
|
||||||
|
7. Nothing in this License Agreement shall be deemed to create any |
||||||
|
relationship of agency, partnership, or joint venture between PSF and |
||||||
|
Licensee. This License Agreement does not grant permission to use PSF |
||||||
|
trademarks or trade name in a trademark sense to endorse or promote |
||||||
|
products or services of Licensee, or any third party. |
||||||
|
|
||||||
|
8. By copying, installing or otherwise using Python, Licensee |
||||||
|
agrees to be bound by the terms and conditions of this License |
||||||
|
Agreement. |
||||||
|
|
||||||
|
|
||||||
|
BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 |
||||||
|
------------------------------------------- |
||||||
|
|
||||||
|
BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 |
||||||
|
|
||||||
|
1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an |
||||||
|
office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the |
||||||
|
Individual or Organization ("Licensee") accessing and otherwise using |
||||||
|
this software in source or binary form and its associated |
||||||
|
documentation ("the Software"). |
||||||
|
|
||||||
|
2. Subject to the terms and conditions of this BeOpen Python License |
||||||
|
Agreement, BeOpen hereby grants Licensee a non-exclusive, |
||||||
|
royalty-free, world-wide license to reproduce, analyze, test, perform |
||||||
|
and/or display publicly, prepare derivative works, distribute, and |
||||||
|
otherwise use the Software alone or in any derivative version, |
||||||
|
provided, however, that the BeOpen Python License is retained in the |
||||||
|
Software, alone or in any derivative version prepared by Licensee. |
||||||
|
|
||||||
|
3. BeOpen is making the Software available to Licensee on an "AS IS" |
||||||
|
basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR |
||||||
|
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND |
||||||
|
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS |
||||||
|
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT |
||||||
|
INFRINGE ANY THIRD PARTY RIGHTS. |
||||||
|
|
||||||
|
4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE |
||||||
|
SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS |
||||||
|
AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY |
||||||
|
DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. |
||||||
|
|
||||||
|
5. This License Agreement will automatically terminate upon a material |
||||||
|
breach of its terms and conditions. |
||||||
|
|
||||||
|
6. This License Agreement shall be governed by and interpreted in all |
||||||
|
respects by the law of the State of California, excluding conflict of |
||||||
|
law provisions. Nothing in this License Agreement shall be deemed to |
||||||
|
create any relationship of agency, partnership, or joint venture |
||||||
|
between BeOpen and Licensee. This License Agreement does not grant |
||||||
|
permission to use BeOpen trademarks or trade names in a trademark |
||||||
|
sense to endorse or promote products or services of Licensee, or any |
||||||
|
third party. As an exception, the "BeOpen Python" logos available at |
||||||
|
http://www.pythonlabs.com/logos.html may be used according to the |
||||||
|
permissions granted on that web page. |
||||||
|
|
||||||
|
7. By copying, installing or otherwise using the software, Licensee |
||||||
|
agrees to be bound by the terms and conditions of this License |
||||||
|
Agreement. |
||||||
|
|
||||||
|
|
||||||
|
CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 |
||||||
|
--------------------------------------- |
||||||
|
|
||||||
|
1. This LICENSE AGREEMENT is between the Corporation for National |
||||||
|
Research Initiatives, having an office at 1895 Preston White Drive, |
||||||
|
Reston, VA 20191 ("CNRI"), and the Individual or Organization |
||||||
|
("Licensee") accessing and otherwise using Python 1.6.1 software in |
||||||
|
source or binary form and its associated documentation. |
||||||
|
|
||||||
|
2. Subject to the terms and conditions of this License Agreement, CNRI |
||||||
|
hereby grants Licensee a nonexclusive, royalty-free, world-wide |
||||||
|
license to reproduce, analyze, test, perform and/or display publicly, |
||||||
|
prepare derivative works, distribute, and otherwise use Python 1.6.1 |
||||||
|
alone or in any derivative version, provided, however, that CNRI's |
||||||
|
License Agreement and CNRI's notice of copyright, i.e., "Copyright (c) |
||||||
|
1995-2001 Corporation for National Research Initiatives; All Rights |
||||||
|
Reserved" are retained in Python 1.6.1 alone or in any derivative |
||||||
|
version prepared by Licensee. Alternately, in lieu of CNRI's License |
||||||
|
Agreement, Licensee may substitute the following text (omitting the |
||||||
|
quotes): "Python 1.6.1 is made available subject to the terms and |
||||||
|
conditions in CNRI's License Agreement. This Agreement together with |
||||||
|
Python 1.6.1 may be located on the internet using the following |
||||||
|
unique, persistent identifier (known as a handle): 1895.22/1013. This |
||||||
|
Agreement may also be obtained from a proxy server on the internet |
||||||
|
using the following URL: http://hdl.handle.net/1895.22/1013". |
||||||
|
|
||||||
|
3. In the event Licensee prepares a derivative work that is based on |
||||||
|
or incorporates Python 1.6.1 or any part thereof, and wants to make |
||||||
|
the derivative work available to others as provided herein, then |
||||||
|
Licensee hereby agrees to include in any such work a brief summary of |
||||||
|
the changes made to Python 1.6.1. |
||||||
|
|
||||||
|
4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" |
||||||
|
basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR |
||||||
|
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND |
||||||
|
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS |
||||||
|
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT |
||||||
|
INFRINGE ANY THIRD PARTY RIGHTS. |
||||||
|
|
||||||
|
5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON |
||||||
|
1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS |
||||||
|
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, |
||||||
|
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. |
||||||
|
|
||||||
|
6. This License Agreement will automatically terminate upon a material |
||||||
|
breach of its terms and conditions. |
||||||
|
|
||||||
|
7. This License Agreement shall be governed by the federal |
||||||
|
intellectual property law of the United States, including without |
||||||
|
limitation the federal copyright law, and, to the extent such |
||||||
|
U.S. federal law does not apply, by the law of the Commonwealth of |
||||||
|
Virginia, excluding Virginia's conflict of law provisions. |
||||||
|
Notwithstanding the foregoing, with regard to derivative works based |
||||||
|
on Python 1.6.1 that incorporate non-separable material that was |
||||||
|
previously distributed under the GNU General Public License (GPL), the |
||||||
|
law of the Commonwealth of Virginia shall govern this License |
||||||
|
Agreement only as to issues arising under or with respect to |
||||||
|
Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this |
||||||
|
License Agreement shall be deemed to create any relationship of |
||||||
|
agency, partnership, or joint venture between CNRI and Licensee. This |
||||||
|
License Agreement does not grant permission to use CNRI trademarks or |
||||||
|
trade name in a trademark sense to endorse or promote products or |
||||||
|
services of Licensee, or any third party. |
||||||
|
|
||||||
|
8. By clicking on the "ACCEPT" button where indicated, or by copying, |
||||||
|
installing or otherwise using Python 1.6.1, Licensee agrees to be |
||||||
|
bound by the terms and conditions of this License Agreement. |
||||||
|
|
||||||
|
ACCEPT |
||||||
|
|
||||||
|
|
||||||
|
CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 |
||||||
|
-------------------------------------------------- |
||||||
|
|
||||||
|
Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, |
||||||
|
The Netherlands. All rights reserved. |
||||||
|
|
||||||
|
Permission to use, copy, modify, and distribute this software and its |
||||||
|
documentation for any purpose and without fee is hereby granted, |
||||||
|
provided that the above copyright notice appear in all copies and that |
||||||
|
both that copyright notice and this permission notice appear in |
||||||
|
supporting documentation, and that the name of Stichting Mathematisch |
||||||
|
Centrum or CWI not be used in advertising or publicity pertaining to |
||||||
|
distribution of the software without specific, written prior |
||||||
|
permission. |
||||||
|
|
||||||
|
STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO |
||||||
|
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND |
||||||
|
FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE |
||||||
|
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES |
||||||
|
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN |
||||||
|
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT |
||||||
|
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. |
||||||
|
|
||||||
|
ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION |
||||||
|
---------------------------------------------------------------------- |
||||||
|
|
||||||
|
Permission to use, copy, modify, and/or distribute this software for any |
||||||
|
purpose with or without fee is hereby granted. |
||||||
|
|
||||||
|
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH |
||||||
|
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY |
||||||
|
AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, |
||||||
|
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM |
||||||
|
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR |
||||||
|
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR |
||||||
|
PERFORMANCE OF THIS SOFTWARE. |
||||||
@ -0,0 +1,4 @@ |
|||||||
|
"""(part of) distutils, taken from the cpython standard library |
||||||
|
|
||||||
|
at commit https://github.com/python/cpython/tree/9d38120e335357a3b294277fd5eff0a10e46e043/Lib/distutils |
||||||
|
""" |
||||||
@ -0,0 +1,347 @@ |
|||||||
|
# |
||||||
|
# distutils/version.py |
||||||
|
# |
||||||
|
# Implements multiple version numbering conventions for the |
||||||
|
# Python Module Distribution Utilities. |
||||||
|
# |
||||||
|
# $Id$ |
||||||
|
# |
||||||
|
|
||||||
|
"""Provides classes to represent module version numbers (one class for |
||||||
|
each style of version numbering). There are currently two such classes |
||||||
|
implemented: StrictVersion and LooseVersion. |
||||||
|
|
||||||
|
Every version number class implements the following interface: |
||||||
|
* the 'parse' method takes a string and parses it to some internal |
||||||
|
representation; if the string is an invalid version number, |
||||||
|
'parse' raises a ValueError exception |
||||||
|
* the class constructor takes an optional string argument which, |
||||||
|
if supplied, is passed to 'parse' |
||||||
|
* __str__ reconstructs the string that was passed to 'parse' (or |
||||||
|
an equivalent string -- ie. one that will generate an equivalent |
||||||
|
version number instance) |
||||||
|
* __repr__ generates Python code to recreate the version number instance |
||||||
|
* _cmp compares the current instance with either another instance |
||||||
|
of the same class or a string (which will be parsed to an instance |
||||||
|
of the same class, thus must follow the same rules) |
||||||
|
""" |
||||||
|
|
||||||
|
import re |
||||||
|
|
||||||
|
class Version: |
||||||
|
"""Abstract base class for version numbering classes. Just provides |
||||||
|
constructor (__init__) and reproducer (__repr__), because those |
||||||
|
seem to be the same for all version numbering classes; and route |
||||||
|
rich comparisons to _cmp. |
||||||
|
""" |
||||||
|
|
||||||
|
def __init__ (self, vstring=None): |
||||||
|
if vstring: |
||||||
|
self.parse(vstring) |
||||||
|
|
||||||
|
def __repr__ (self): |
||||||
|
return "%s ('%s')" % (self.__class__.__name__, str(self)) |
||||||
|
|
||||||
|
def __eq__(self, other): |
||||||
|
c = self._cmp(other) |
||||||
|
if c is NotImplemented: |
||||||
|
return c |
||||||
|
return c == 0 |
||||||
|
|
||||||
|
def __lt__(self, other): |
||||||
|
c = self._cmp(other) |
||||||
|
if c is NotImplemented: |
||||||
|
return c |
||||||
|
return c < 0 |
||||||
|
|
||||||
|
def __le__(self, other): |
||||||
|
c = self._cmp(other) |
||||||
|
if c is NotImplemented: |
||||||
|
return c |
||||||
|
return c <= 0 |
||||||
|
|
||||||
|
def __gt__(self, other): |
||||||
|
c = self._cmp(other) |
||||||
|
if c is NotImplemented: |
||||||
|
return c |
||||||
|
return c > 0 |
||||||
|
|
||||||
|
def __ge__(self, other): |
||||||
|
c = self._cmp(other) |
||||||
|
if c is NotImplemented: |
||||||
|
return c |
||||||
|
return c >= 0 |
||||||
|
|
||||||
|
|
||||||
|
# Interface for version-number classes -- must be implemented |
||||||
|
# by the following classes (the concrete ones -- Version should |
||||||
|
# be treated as an abstract class). |
||||||
|
# __init__ (string) - create and take same action as 'parse' |
||||||
|
# (string parameter is optional) |
||||||
|
# parse (string) - convert a string representation to whatever |
||||||
|
# internal representation is appropriate for |
||||||
|
# this style of version numbering |
||||||
|
# __str__ (self) - convert back to a string; should be very similar |
||||||
|
# (if not identical to) the string supplied to parse |
||||||
|
# __repr__ (self) - generate Python code to recreate |
||||||
|
# the instance |
||||||
|
# _cmp (self, other) - compare two version numbers ('other' may |
||||||
|
# be an unparsed version string, or another |
||||||
|
# instance of your version class) |
||||||
|
|
||||||
|
|
||||||
|
class StrictVersion (Version): |
||||||
|
|
||||||
|
"""Version numbering for anal retentives and software idealists. |
||||||
|
Implements the standard interface for version number classes as |
||||||
|
described above. A version number consists of two or three |
||||||
|
dot-separated numeric components, with an optional "pre-release" tag |
||||||
|
on the end. The pre-release tag consists of the letter 'a' or 'b' |
||||||
|
followed by a number. If the numeric components of two version |
||||||
|
numbers are equal, then one with a pre-release tag will always |
||||||
|
be deemed earlier (lesser) than one without. |
||||||
|
|
||||||
|
The following are valid version numbers (shown in the order that |
||||||
|
would be obtained by sorting according to the supplied cmp function): |
||||||
|
|
||||||
|
0.4 0.4.0 (these two are equivalent) |
||||||
|
0.4.1 |
||||||
|
0.5a1 |
||||||
|
0.5b3 |
||||||
|
0.5 |
||||||
|
0.9.6 |
||||||
|
1.0 |
||||||
|
1.0.4a3 |
||||||
|
1.0.4b1 |
||||||
|
1.0.4 |
||||||
|
|
||||||
|
The following are examples of invalid version numbers: |
||||||
|
|
||||||
|
1 |
||||||
|
2.7.2.2 |
||||||
|
1.3.a4 |
||||||
|
1.3pl1 |
||||||
|
1.3c4 |
||||||
|
|
||||||
|
The rationale for this version numbering system will be explained |
||||||
|
in the distutils documentation. |
||||||
|
""" |
||||||
|
|
||||||
|
version_re = re.compile(r'^(\d+) \. (\d+) (\. (\d+))? ([ab](\d+))?$', |
||||||
|
re.VERBOSE | re.ASCII) |
||||||
|
|
||||||
|
|
||||||
|
def parse (self, vstring): |
||||||
|
match = self.version_re.match(vstring) |
||||||
|
if not match: |
||||||
|
raise ValueError("invalid version number '%s'" % vstring) |
||||||
|
|
||||||
|
(major, minor, patch, prerelease, prerelease_num) = \ |
||||||
|
match.group(1, 2, 4, 5, 6) |
||||||
|
|
||||||
|
if patch: |
||||||
|
self.version = tuple(map(int, [major, minor, patch])) |
||||||
|
else: |
||||||
|
self.version = tuple(map(int, [major, minor])) + (0,) |
||||||
|
|
||||||
|
if prerelease: |
||||||
|
self.prerelease = (prerelease[0], int(prerelease_num)) |
||||||
|
else: |
||||||
|
self.prerelease = None |
||||||
|
|
||||||
|
|
||||||
|
def __str__ (self): |
||||||
|
|
||||||
|
if self.version[2] == 0: |
||||||
|
vstring = '.'.join(map(str, self.version[0:2])) |
||||||
|
else: |
||||||
|
vstring = '.'.join(map(str, self.version)) |
||||||
|
|
||||||
|
if self.prerelease: |
||||||
|
vstring = vstring + self.prerelease[0] + str(self.prerelease[1]) |
||||||
|
|
||||||
|
return vstring |
||||||
|
|
||||||
|
|
||||||
|
def _cmp (self, other): |
||||||
|
if isinstance(other, str): |
||||||
|
other = StrictVersion(other) |
||||||
|
elif not isinstance(other, StrictVersion): |
||||||
|
return NotImplemented |
||||||
|
|
||||||
|
if self.version != other.version: |
||||||
|
# numeric versions don't match |
||||||
|
# prerelease stuff doesn't matter |
||||||
|
if self.version < other.version: |
||||||
|
return -1 |
||||||
|
else: |
||||||
|
return 1 |
||||||
|
|
||||||
|
# have to compare prerelease |
||||||
|
# case 1: neither has prerelease; they're equal |
||||||
|
# case 2: self has prerelease, other doesn't; other is greater |
||||||
|
# case 3: self doesn't have prerelease, other does: self is greater |
||||||
|
# case 4: both have prerelease: must compare them! |
||||||
|
|
||||||
|
if (not self.prerelease and not other.prerelease): |
||||||
|
return 0 |
||||||
|
elif (self.prerelease and not other.prerelease): |
||||||
|
return -1 |
||||||
|
elif (not self.prerelease and other.prerelease): |
||||||
|
return 1 |
||||||
|
elif (self.prerelease and other.prerelease): |
||||||
|
if self.prerelease == other.prerelease: |
||||||
|
return 0 |
||||||
|
elif self.prerelease < other.prerelease: |
||||||
|
return -1 |
||||||
|
else: |
||||||
|
return 1 |
||||||
|
else: |
||||||
|
assert False, "never get here" |
||||||
|
|
||||||
|
# end class StrictVersion |
||||||
|
|
||||||
|
|
||||||
|
# The rules according to Greg Stein: |
||||||
|
# 1) a version number has 1 or more numbers separated by a period or by |
||||||
|
# sequences of letters. If only periods, then these are compared |
||||||
|
# left-to-right to determine an ordering. |
||||||
|
# 2) sequences of letters are part of the tuple for comparison and are |
||||||
|
# compared lexicographically |
||||||
|
# 3) recognize the numeric components may have leading zeroes |
||||||
|
# |
||||||
|
# The LooseVersion class below implements these rules: a version number |
||||||
|
# string is split up into a tuple of integer and string components, and |
||||||
|
# comparison is a simple tuple comparison. This means that version |
||||||
|
# numbers behave in a predictable and obvious way, but a way that might |
||||||
|
# not necessarily be how people *want* version numbers to behave. There |
||||||
|
# wouldn't be a problem if people could stick to purely numeric version |
||||||
|
# numbers: just split on period and compare the numbers as tuples. |
||||||
|
# However, people insist on putting letters into their version numbers; |
||||||
|
# the most common purpose seems to be: |
||||||
|
# - indicating a "pre-release" version |
||||||
|
# ('alpha', 'beta', 'a', 'b', 'pre', 'p') |
||||||
|
# - indicating a post-release patch ('p', 'pl', 'patch') |
||||||
|
# but of course this can't cover all version number schemes, and there's |
||||||
|
# no way to know what a programmer means without asking him. |
||||||
|
# |
||||||
|
# The problem is what to do with letters (and other non-numeric |
||||||
|
# characters) in a version number. The current implementation does the |
||||||
|
# obvious and predictable thing: keep them as strings and compare |
||||||
|
# lexically within a tuple comparison. This has the desired effect if |
||||||
|
# an appended letter sequence implies something "post-release": |
||||||
|
# eg. "0.99" < "0.99pl14" < "1.0", and "5.001" < "5.001m" < "5.002". |
||||||
|
# |
||||||
|
# However, if letters in a version number imply a pre-release version, |
||||||
|
# the "obvious" thing isn't correct. Eg. you would expect that |
||||||
|
# "1.5.1" < "1.5.2a2" < "1.5.2", but under the tuple/lexical comparison |
||||||
|
# implemented here, this just isn't so. |
||||||
|
# |
||||||
|
# Two possible solutions come to mind. The first is to tie the |
||||||
|
# comparison algorithm to a particular set of semantic rules, as has |
||||||
|
# been done in the StrictVersion class above. This works great as long |
||||||
|
# as everyone can go along with bondage and discipline. Hopefully a |
||||||
|
# (large) subset of Python module programmers will agree that the |
||||||
|
# particular flavour of bondage and discipline provided by StrictVersion |
||||||
|
# provides enough benefit to be worth using, and will submit their |
||||||
|
# version numbering scheme to its domination. The free-thinking |
||||||
|
# anarchists in the lot will never give in, though, and something needs |
||||||
|
# to be done to accommodate them. |
||||||
|
# |
||||||
|
# Perhaps a "moderately strict" version class could be implemented that |
||||||
|
# lets almost anything slide (syntactically), and makes some heuristic |
||||||
|
# assumptions about non-digits in version number strings. This could |
||||||
|
# sink into special-case-hell, though; if I was as talented and |
||||||
|
# idiosyncratic as Larry Wall, I'd go ahead and implement a class that |
||||||
|
# somehow knows that "1.2.1" < "1.2.2a2" < "1.2.2" < "1.2.2pl3", and is |
||||||
|
# just as happy dealing with things like "2g6" and "1.13++". I don't |
||||||
|
# think I'm smart enough to do it right though. |
||||||
|
# |
||||||
|
# In any case, I've coded the test suite for this module (see |
||||||
|
# ../test/test_version.py) specifically to fail on things like comparing |
||||||
|
# "1.2a2" and "1.2". That's not because the *code* is doing anything |
||||||
|
# wrong, it's because the simple, obvious design doesn't match my |
||||||
|
# complicated, hairy expectations for real-world version numbers. It |
||||||
|
# would be a snap to fix the test suite to say, "Yep, LooseVersion does |
||||||
|
# the Right Thing" (ie. the code matches the conception). But I'd rather |
||||||
|
# have a conception that matches common notions about version numbers. |
||||||
|
|
||||||
|
class LooseVersion (Version): |
||||||
|
|
||||||
|
"""Version numbering for anarchists and software realists. |
||||||
|
Implements the standard interface for version number classes as |
||||||
|
described above. A version number consists of a series of numbers, |
||||||
|
separated by either periods or strings of letters. When comparing |
||||||
|
version numbers, the numeric components will be compared |
||||||
|
numerically, and the alphabetic components lexically. The following |
||||||
|
are all valid version numbers, in no particular order: |
||||||
|
|
||||||
|
1.5.1 |
||||||
|
1.5.2b2 |
||||||
|
161 |
||||||
|
3.10a |
||||||
|
8.02 |
||||||
|
3.4j |
||||||
|
1996.07.12 |
||||||
|
3.2.pl0 |
||||||
|
3.1.1.6 |
||||||
|
2g6 |
||||||
|
11g |
||||||
|
0.960923 |
||||||
|
2.2beta29 |
||||||
|
1.13++ |
||||||
|
5.5.kw |
||||||
|
2.0b1pl0 |
||||||
|
|
||||||
|
In fact, there is no such thing as an invalid version number under |
||||||
|
this scheme; the rules for comparison are simple and predictable, |
||||||
|
but may not always give the results you want (for some definition |
||||||
|
of "want"). |
||||||
|
""" |
||||||
|
|
||||||
|
component_re = re.compile(r'(\d+ | [a-z]+ | \.)', re.VERBOSE) |
||||||
|
|
||||||
|
def __init__ (self, vstring=None): |
||||||
|
if vstring: |
||||||
|
self.parse(vstring) |
||||||
|
|
||||||
|
|
||||||
|
def parse (self, vstring): |
||||||
|
# I've given up on thinking I can reconstruct the version string |
||||||
|
# from the parsed tuple -- so I just store the string here for |
||||||
|
# use by __str__ |
||||||
|
self.vstring = vstring |
||||||
|
components = [x for x in self.component_re.split(vstring) |
||||||
|
if x and x != '.'] |
||||||
|
for i, obj in enumerate(components): |
||||||
|
try: |
||||||
|
components[i] = int(obj) |
||||||
|
except ValueError: |
||||||
|
pass |
||||||
|
|
||||||
|
self.version = components |
||||||
|
|
||||||
|
|
||||||
|
def __str__ (self): |
||||||
|
return self.vstring |
||||||
|
|
||||||
|
|
||||||
|
def __repr__ (self): |
||||||
|
return "LooseVersion ('%s')" % str(self) |
||||||
|
|
||||||
|
|
||||||
|
def _cmp (self, other): |
||||||
|
if isinstance(other, str): |
||||||
|
other = LooseVersion(other) |
||||||
|
elif not isinstance(other, LooseVersion): |
||||||
|
return NotImplemented |
||||||
|
|
||||||
|
if self.version == other.version: |
||||||
|
return 0 |
||||||
|
if self.version < other.version: |
||||||
|
return -1 |
||||||
|
if self.version > other.version: |
||||||
|
return 1 |
||||||
|
|
||||||
|
|
||||||
|
# end class LooseVersion |
||||||
Loading…
Reference in new issue