ConfigUpdater 4.0__py3-none-any.whl

configupdater-4.0.dist-info/METADATA

@@ -0,0 +1,349 @@
+Metadata-Version: 2.5
+Name: ConfigUpdater
+Version: 4.0
+Summary: Parser like ConfigParser but for updating configuration files
+Project-URL: Homepage, https://github.com/pyscaffold/configupdater
+Project-URL: Documentation, https://configupdater.readthedocs.io/
+Project-URL: Source, https://github.com/pyscaffold/configupdater/
+Project-URL: Issues, https://github.com/pyscaffold/configupdater/issues
+Project-URL: Changelog, https://configupdater.readthedocs.io/en/latest/changelog.html
+Project-URL: Download, https://pypi.org/project/configupdater/#files
+Project-URL: Conda-Forge, https://anaconda.org/conda-forge/configupdater
+Author-email: Florian Wilhelm <florian.wilhelm@gmail.com>, Anderson Bravalheri <andersonbravalheri@gmail.com>
+License-Expression: MIT
+License-File: LICENSE.txt
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
+<div align="center">
+<img src="https://raw.githubusercontent.com/pyscaffold/configupdater/master/docs/gfx/banner-640x323.png" alt="Configupdater logo" width="500" role="img">
+</div>
+<br/>
+
+|         |                                    |
+|---------|------------------------------------|
+| CI/CD   | [![Tests][Tests-image]][Tests-link] [![Coverage][Coverage-image]][Coverage-link] [![Publish Package][Publish-image]][Publish-link] [![GitHub Sponsors][sponsor-image]][sponsor-link]  |
+| Package | [![PyPI - Version][PyPI_ver-image]][PyPI_ver-link] [![Conda - Version][Conda-image]][Conda-link] [![PyPI - Downloads][PyPI_down-image]][PyPI_down-link] [![PyPI - Python Version][PyPI_py-image]][PyPI_py-link] |
+| Details | [![uv][uv-image]][uv-link] [![Linting - Ruff][ruff-image]][ruff-link] [![test - pytest][pytest-image]][pytest-link] [![Pre-Commit][precommit-image]][precommit-link] [![Types - Mypy][mypy-image]][mypy-link] [![License - MIT][MIT-image]][MIT-link] [![Docs - RTD][rtd-image]][rtd-link] |
+
+The sole purpose of [ConfigUpdater] is to easily
+update an INI config file with no changes to the original file except
+the intended ones. This means comments, the ordering of sections and
+key/value-pairs as wells as their cases are kept as in the original
+file. Thus ConfigUpdater provides complementary functionality to
+Python\'s [ConfigParser], which is primarily meant for reading config
+files and writing *new* ones.
+
+# Features
+
+The key differences to [ConfigParser] are:
+
+- minimal invasive changes in the update configuration file,
+- proper handling of comments,
+- only a single config file can be updated at a time,
+- the original case of sections and keys are kept,
+- control over the position of a new section/key
+
+Following features are **deliberately not** implemented:
+
+- interpolation of values,
+- propagation of parameters from the default section,
+- conversions of values,
+- passing key/value-pairs with `default` argument,
+- non-strict mode allowing duplicate sections and keys.
+
+# Usage
+
+First install the package with either:
+
+```console
+pip install configupdater
+```
+
+or add it to a project managed with [uv]:
+
+```console
+uv add configupdater
+```
+
+or:
+
+```console
+conda install -c conda-forge configupdater
+```
+
+Now we can simply do:
+
+```python
+from configupdater import ConfigUpdater
+
+updater = ConfigUpdater()
+updater.read("setup.cfg")
+```
+
+which would read the file `setup.cfg` that is found in many projects.
+
+To change the value of an existing key we can simply do:
+
+```python
+updater["metadata"]["author"].value = "Alan Turing"
+```
+
+At any point we can print the current state of the configuration file
+with:
+
+```python
+print(updater)
+```
+
+To update the read-in file, with the encoding it was read with, just call
+`updater.update_file()` or `updater.write(open('filename','w'))` to write
+the changed configuration file to another destination. Before actually
+writing, ConfigUpdater will automatically check that the updated
+configuration file is still valid by parsing it with the help of ConfigParser.
+
+Many of ConfigParser\'s methods still exists and it\'s best to look them
+up in the [module reference]. Let\'s look at some examples.
+
+## Adding and removing options
+
+Let\'s say we have the following configuration in a string:
+
+```python
+cfg = """
+[metadata]
+author = Ada Lovelace
+summary = The Analytical Engine
+"""
+```
+
+We can add an *license* option, i.e. a key/value pair, in the same way
+we would do with ConfigParser:
+
+```python
+updater = ConfigUpdater()
+updater.read_string(cfg)
+updater["metadata"]["license"] = "MIT"
+```
+
+A simple `print(updater)` will give show you that the new option was
+appended to the end:
+
+```ini
+[metadata]
+author = Ada Lovelace
+summary = The Analytical Engine
+license = MIT
+```
+
+Since the license is really important to us let\'s say we want to add it
+before the `summary` and even add a short comment before it:
+
+```python
+updater = ConfigUpdater()
+updater.read_string(cfg)
+(
+    updater["metadata"]["summary"]
+    .add_before.comment("Ada would have loved MIT")
+    .option("license", "MIT")
+)
+```
+
+which would result in:
+
+```ini
+[metadata]
+author = Ada Lovelace
+# Ada would have loved MIT
+license = MIT
+summary = The Analytical Engine
+```
+
+Using `add_after` would give the same result and looks like:
+
+```python
+updater = ConfigUpdater()
+updater.read_string(cfg)
+(
+    updater["metadata"]["author"]
+    .add_after.comment("Ada would have loved MIT")
+    .option("license", "MIT")
+)
+```
+
+Let\'s say we want to rename `summary` to the more common
+`description`:
+
+```python
+updater = ConfigUpdater()
+updater.read_string(cfg)
+updater["metadata"]["summary"].key = "description"
+```
+
+If we wanted no summary at all, we could just do
+`del updater["metadata"]["summary"]`.
+
+## Adding and removing sections
+
+Adding and remove sections just works like adding and removing options
+but on a higher level. Sticking to our *Ada Lovelace* example, let\'s
+say we want to add a section `options` just before `metadata` with a
+comment and two new lines to separate it from `metadata`:
+
+```python
+updater = ConfigUpdater()
+updater.read_string(cfg)
+(
+    updater["metadata"]
+    .add_before.comment("Some specific project options")
+    .section("options")
+    .space(2)
+)
+```
+
+As expected, this results in:
+
+```ini
+# Some specific project options
+[options]
+
+
+[metadata]
+author = Ada Lovelace
+summary = The Analytical Engine
+```
+
+We could now fill the new section with options like we learnt before. If
+we wanted to rename an existing section we could do this with the help
+of the `name` attribute:
+
+```python
+updater["metadata"].name = "MetaData"
+```
+
+Sometimes it might be useful to inject a new section not in a
+programmatic way but more declarative. Let\'s assume we have thus
+defined our new section in a multi-line string:
+
+```python
+sphinx_sect_str = """
+[build_sphinx]
+source_dir = docs
+build_dir = docs/_build
+"""
+```
+
+With the help of two ConfigUpdater objects we can easily inject this
+section into our example:
+
+```python
+sphinx = ConfigUpdater()
+sphinx.read_string(sphinx_sect_str)
+sphinx_sect = sphinx["build_sphinx"]
+
+updater = ConfigUpdater()
+updater.read_string(cfg)
+
+(updater["metadata"].add_after.space().section(sphinx_sect.detach()))
+```
+
+The `detach` method will remove the `build_sphinx` section from the
+first object and add it to the second object. This results in:
+
+```ini
+[metadata]
+author = Ada Lovelace
+summary = The Analytical Engine
+
+[build_sphinx]
+source_dir = docs
+build_dir = docs/_build
+```
+
+Alternatively, if you want to preserve `build_sphinx` in both
+`ConfigUpdater` objects (i.e., prevent it from being removed from the
+first while still adding a copy to the second), you call also rely on
+stdlib\'s `copy.deepcopy` function instead of `detach`:
+
+```python
+from copy import deepcopy
+
+sphinx = ConfigUpdater()
+sphinx.read_string(sphinx_sect_str)
+sphinx_sect = sphinx["build_sphinx"]
+
+updater = ConfigUpdater()
+updater.read_string(cfg)
+
+(updater["metadata"].add_after.space().section(deepcopy(sphinx_sect)))
+```
+
+This technique can be used for all objects inside ConfigUpdater:
+sections, options, comments and blank spaces.
+
+Shallow copies are discouraged in the context of ConfigUpdater because
+each configuration block keeps a reference to its container to allow
+easy document editing. When doing editions (such as adding or changing
+options and comments) based on a shallow copy, the results can be
+unreliable and unexpected.
+
+For more examples on how the API of ConfigUpdater works it\'s best to
+take a look into the [unit tests] and read the references.
+
+# Notes
+
+ConfigUpdater started out as a helper for [PyScaffold], which still uses
+it to update the `setup.cfg` of existing projects. Since then it has
+become a useful tool in its own right for everyone who needs to change
+configuration files programmatically without losing the comments and
+formatting that humans put into them.
+
+[ConfigUpdater]: https://configupdater.readthedocs.io/
+[ConfigParser]: https://docs.python.org/3/library/configparser.html
+[PyScaffold]: https://pyscaffold.org/
+[uv]: https://docs.astral.sh/uv/
+[module reference]: https://configupdater.readthedocs.io/en/latest/api.html#configupdater.configupdater.ConfigUpdater
+[unit tests]: https://github.com/pyscaffold/configupdater/blob/main/tests/test_configupdater.py
+
+[Tests-image]: https://github.com/pyscaffold/configupdater/actions/workflows/ci.yml/badge.svg
+[Tests-link]: https://github.com/pyscaffold/configupdater/actions/workflows/ci.yml
+[Coverage-image]: https://img.shields.io/coveralls/github/pyscaffold/configupdater/main.svg
+[Coverage-link]: https://coveralls.io/r/pyscaffold/configupdater
+[Publish-image]: https://github.com/pyscaffold/configupdater/actions/workflows/publish-package.yml/badge.svg
+[Publish-link]: https://github.com/pyscaffold/configupdater/actions/workflows/publish-package.yml
+[PyPI_ver-image]:https://img.shields.io/pypi/v/configupdater.svg?logo=pypi&label=PyPI&logoColor=gold
+[PyPI_ver-link]: https://pypi.org/project/configupdater/
+[Conda-image]: https://img.shields.io/conda/vn/conda-forge/configupdater.svg?logo=Anaconda&label=Conda-Forge&logoColor=44A833
+[Conda-link]: https://anaconda.org/conda-forge/configupdater/
+[PyPI_down-image]: https://img.shields.io/pypi/dm/configupdater.svg?color=blue&label=Downloads&logo=pypi&logoColor=gold
+[PyPI_down-link]: https://clickpy.clickhouse.com/dashboard/configupdater
+[PyPI_py-image]: https://img.shields.io/pypi/pyversions/configupdater.svg?logo=python&label=Python&logoColor=gold
+[PyPI_py-link]: https://pypi.org/project/configupdater/
+[uv-image]: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/uv/main/assets/badge/v0.json
+[uv-link]: https://github.com/astral-sh/uv
+[ruff-image]: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json
+[ruff-link]: https://github.com/charliermarsh/ruff
+[mypy-image]: https://img.shields.io/badge/Types-mypy-blue.svg
+[mypy-link]: https://mypy-lang.org/
+[pytest-image]: https://img.shields.io/static/v1?label=‎&message=Pytest&logo=Pytest&color=0A9EDC&logoColor=white
+[pytest-link]:  https://docs.pytest.org/
+[rtd-image]: https://readthedocs.org/projects/configupdater/badge/?version=latest
+[rtd-link]: https://configupdater.readthedocs.io/
+[precommit-image]: https://img.shields.io/static/v1?label=‎&message=pre-commit&logo=pre-commit&color=76877c
+[precommit-link]: https://pre-commit.com/
+[MIT-image]: https://img.shields.io/badge/License-MIT-9400d3.svg
+[MIT-link]: LICENSE.txt
+[sponsor-image]: https://img.shields.io/static/v1?label=Sponsor&message=%E2%9D%A4&logo=GitHub&color=ff69b4
+[sponsor-link]: https://github.com/sponsors/FlorianWilhelm

configupdater-4.0.dist-info/RECORD

@@ -0,0 +1,14 @@
+configupdater/__init__.py,sha256=Waiyjx25q2Xa_NRlZ9GBuqyrCvPx7n3OG2rnYtTFDZA,526
+configupdater/block.py,sha256=5GICM-FCKzAMOfZq7EfsSm9SiPR7JkwoIg7PCwR47h8,6674
+configupdater/builder.py,sha256=TE5RZySHeaaaHCC0eZZSP0b4xulxpJoYll3DDNr7Psk,4144
+configupdater/configupdater.py,sha256=_PIgIzVStKvOOdyJKtpc0X4m1X_YDWlO-7V-nmnScR4,8233
+configupdater/container.py,sha256=pqPerih6m0sG6ET9PeDch0kjyZ3hipoJ_Fb28H3ZTIY,2736
+configupdater/document.py,sha256=69rtaATQj8zRpm6Zd54tQvBsEHP7l4773wbJJbRL9I8,15002
+configupdater/option.py,sha256=iEogFOyFRny2K2G-UieJcmtAPN2QutkJ_DdQwIM-dZg,9272
+configupdater/parser.py,sha256=O6ujmzq7QOcm-IQ0h3tq5lfbBJEHrUvuH4Rr_VuTpmE,25009
+configupdater/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+configupdater/section.py,sha256=BjuVmEuT03VBEInS_me9G9RmTsOFQSZS1oA3pu6zFBQ,13049
+configupdater-4.0.dist-info/METADATA,sha256=2YKXjQjlhVEdaWCEfjgRMeGWBl0e_HT-9gX44bIybC4,12124
+configupdater-4.0.dist-info/WHEEL,sha256=W3fkpkm7-wf9vBI5Z-7s0eWkeM-spu78I8Neb98DeEg,87
+configupdater-4.0.dist-info/licenses/LICENSE.txt,sha256=t_IAs6aOhF6A7JaCD91OZ7bNsZ2IjmavMoFtQDXtRBY,14402
+configupdater-4.0.dist-info/RECORD,,

configupdater-4.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.32.4
+Root-Is-Purelib: true
+Tag: py3-none-any

configupdater-4.0.dist-info/licenses/LICENSE.txt

@@ -0,0 +1,289 @@
+ConfigUpdater is licensed under the MIT license; see below for details.
+
+ConfigUpdater includes code derived from the Python standard library, which is
+licensed under the Python license, a permissive open source license.
+The copyright and license are included at the bottom of this file for compliance
+with Python's terms.
+
+----------------------------------------------------------------------
+
+The MIT License (MIT)
+
+Copyright (c) 2018 Florian Wilhelm
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+----------------------------------------------------------------------
+
+Copyright (c) 2001-present Python Software Foundation; All Rights Reserved
+
+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 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 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.