zope.proxy 5.1__tar.gz → 5.3__tar.gz

{zope.proxy-5.1 → zope.proxy-5.3}/.coveragerc

@@ -15,6 +15,7 @@ source =
 [report]
 show_missing = true
 precision = 2
+ignore_errors = True
 exclude_lines =
     except ImportError:
     if __name__ == '__main__':

{zope.proxy-5.1 → zope.proxy-5.3}/.manylinux-install.sh

@@ -28,6 +28,7 @@ yum -y install libffi-devel
 
 tox_env_map() {
     case $1 in
+        *"cp313"*) echo 'py313';;
         *"cp37"*) echo 'py37';;
         *"cp38"*) echo 'py38';;
         *"cp39"*) echo 'py39';;
@@ -41,14 +42,20 @@ tox_env_map() {
 # Compile wheels
 for PYBIN in /opt/python/*/bin; do
     if \
-       [[ "${PYBIN}" == *"cp311"* ]] || \
-       [[ "${PYBIN}" == *"cp312"* ]] || \
-       [[ "${PYBIN}" == *"cp37"* ]] || \
-       [[ "${PYBIN}" == *"cp38"* ]] || \
-       [[ "${PYBIN}" == *"cp39"* ]] || \
-       [[ "${PYBIN}" == *"cp310"* ]] ; then
-        "${PYBIN}/pip" install -e /io/
-        "${PYBIN}/pip" wheel /io/ -w wheelhouse/
+       [[ "${PYBIN}" == *"cp313/"* ]] || \
+       [[ "${PYBIN}" == *"cp311/"* ]] || \
+       [[ "${PYBIN}" == *"cp312/"* ]] || \
+       [[ "${PYBIN}" == *"cp37/"* ]] || \
+       [[ "${PYBIN}" == *"cp38/"* ]] || \
+       [[ "${PYBIN}" == *"cp39/"* ]] || \
+       [[ "${PYBIN}" == *"cp310/"* ]] ; then
+        if [[ "${PYBIN}" == *"cp313/"* ]] ; then
+            "${PYBIN}/pip" install --pre -e /io/
+            "${PYBIN}/pip" wheel /io/ --pre -w wheelhouse/
+        else
+            "${PYBIN}/pip" install -e /io/
+            "${PYBIN}/pip" wheel /io/ -w wheelhouse/
+        fi
         if [ `uname -m` == 'aarch64' ]; then
           cd /io/
           ${PYBIN}/pip install tox

{zope.proxy-5.1 → zope.proxy-5.3}/CHANGES.rst

@@ -2,6 +2,21 @@
  Changes
 =========
 
+5.3 (2024-08-07)
+================
+
+- Build Windows wheels on GHA.
+
+- Correct return type for ``wrap_hash`` (fixes build on ``i386``).
+  (`#61 <https://github.com/zopefoundation/zope.proxy/issues/61>`_)
+
+
+5.2 (2024-02-09)
+================
+
+- Add preliminary support for Python 3.13 as of 3.13a3.
+
+
 5.1 (2023-10-05)
 ================
 

{zope.proxy-5.1 → zope.proxy-5.3}/MANIFEST.in

@@ -5,7 +5,6 @@ include *.rst
 include *.txt
 include buildout.cfg
 include tox.ini
-include appveyor.yml
 include .coveragerc
 
 recursive-include docs *.py

{zope.proxy-5.1 → zope.proxy-5.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: zope.proxy
-Version: 5.1
+Version: 5.3
 Summary: Generic Transparent Proxies
 Home-page: http://github.com/zopefoundation/zope.proxy
 Author: Zope Foundation and Contributors
@@ -80,6 +80,21 @@ Complete documentation is at https://zopeproxy.readthedocs.io
  Changes
 =========
 
+5.3 (2024-08-07)
+================
+
+- Build Windows wheels on GHA.
+
+- Correct return type for ``wrap_hash`` (fixes build on ``i386``).
+  (`#61 <https://github.com/zopefoundation/zope.proxy/issues/61>`_)
+
+
+5.2 (2024-02-09)
+================
+
+- Add preliminary support for Python 3.13 as of 3.13a3.
+
+
 5.1 (2023-10-05)
 ================
 

{zope.proxy-5.1 → zope.proxy-5.3}/setup.cfg

@@ -1,6 +1,3 @@
-[bdist_wheel]
-universal = 0
-
 [zest.releaser]
 create-wheel = no
 

{zope.proxy-5.1 → zope.proxy-5.3}/setup.py

@@ -79,7 +79,7 @@ else:
     headers = [os.path.join('src', 'zope', 'proxy', 'proxy.h')]
 
 setup(name='zope.proxy',
-      version='5.1',
+      version='5.3',
       author='Zope Foundation and Contributors',
       author_email='zope-dev@zope.org',
       description='Generic Transparent Proxies',

{zope.proxy-5.1 → zope.proxy-5.3}/src/zope/proxy/_zope_proxy_proxy.c

@@ -311,7 +311,7 @@ wrap_repr(PyObject *wrapper)
     return PyObject_Repr(Proxy_GET_OBJECT(wrapper));
 }
 
-static long
+static Py_hash_t
 wrap_hash(PyObject *self)
 {
     return PyObject_Hash(Proxy_GET_OBJECT(self));
@@ -321,8 +321,7 @@ static PyObject *
 wrap_call(PyObject *self, PyObject *args, PyObject *kw)
 {
     if (kw)
-        return PyEval_CallObjectWithKeywords(Proxy_GET_OBJECT(self),
-                                             args, kw);
+        return PyObject_Call(Proxy_GET_OBJECT(self), args, kw);
     else
         return PyObject_CallObject(Proxy_GET_OBJECT(self), args);
 }

{zope.proxy-5.1 → zope.proxy-5.3}/src/zope/proxy/tests/test_proxy.py

@@ -44,12 +44,6 @@ class PyProxyBaseTestCase(unittest.TestCase):
     getslice = '__getitem__'
     setslice = '__setitem__'
 
-    # Avoid DeprecationWarning for assertRaisesRegexp on Python 3 while
-    # coping with Python 2 not having the Regex spelling variant
-    assertRaisesRegex = getattr(
-        unittest.TestCase, 'assertRaisesRegex',
-        getattr(unittest.TestCase, 'assertRaisesRegexp', None))
-
     def _getTargetClass(self):
         from zope.proxy import PyProxyBase
         return PyProxyBase

{zope.proxy-5.1 → zope.proxy-5.3}/src/zope.proxy.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: zope.proxy
-Version: 5.1
+Version: 5.3
 Summary: Generic Transparent Proxies
 Home-page: http://github.com/zopefoundation/zope.proxy
 Author: Zope Foundation and Contributors
@@ -80,6 +80,21 @@ Complete documentation is at https://zopeproxy.readthedocs.io
  Changes
 =========
 
+5.3 (2024-08-07)
+================
+
+- Build Windows wheels on GHA.
+
+- Correct return type for ``wrap_hash`` (fixes build on ``i386``).
+  (`#61 <https://github.com/zopefoundation/zope.proxy/issues/61>`_)
+
+
+5.2 (2024-02-09)
+================
+
+- Add preliminary support for Python 3.13 as of 3.13a3.
+
+
 5.1 (2023-10-05)
 ================
 

{zope.proxy-5.1 → zope.proxy-5.3}/src/zope.proxy.egg-info/SOURCES.txt

@@ -8,7 +8,6 @@ COPYRIGHT.txt
 LICENSE.txt
 MANIFEST.in
 README.rst
-appveyor.yml
 buildout.cfg
 setup.cfg
 setup.py
@@ -22,12 +21,6 @@ docs/index.rst
 docs/make.bat
 docs/narr.rst
 docs/requirements.txt
-docs/_build/doctest/output.txt
-docs/_build/html/_sources/api.rst.txt
-docs/_build/html/_sources/changes.rst.txt
-docs/_build/html/_sources/hacking.rst.txt
-docs/_build/html/_sources/index.rst.txt
-docs/_build/html/_sources/narr.rst.txt
 src/zope/__init__.py
 src/zope.proxy.egg-info/PKG-INFO
 src/zope.proxy.egg-info/SOURCES.txt

{zope.proxy-5.1 → zope.proxy-5.3}/tox.ini

@@ -10,14 +10,18 @@ envlist =
     py310,py310-pure
     py311,py311-pure
     py312,py312-pure
+    py313,py313-pure
     pypy3
     docs
     coverage
 
 [testenv]
 usedevelop = true
+pip_pre = py313: true
 deps =
+    setuptools < 69
     py37: urllib3 < 2
+    Sphinx
 setenv =
     pure: PURE_PYTHON=1
     !pure-!pypy3: PURE_PYTHON=0
@@ -44,21 +48,32 @@ commands =
     coverage run -m zope.testrunner --test-path=src {posargs:-vc}
     coverage html -i
     coverage report -i -m --fail-under=99
+[testenv:release-check]
+description = ensure that the distribution is ready to release
+basepython = python3
+skip_install = true
+deps =
+    twine
+    build
+    check-manifest
+    check-python-versions >= 0.20.0
+    wheel
+commands_pre =
+commands =
+    check-manifest
+    check-python-versions --only setup.py,tox.ini,.github/workflows/tests.yml
+    python -m build --sdist --no-isolation
+    twine check dist/*
 
 [testenv:lint]
 basepython = python3
 skip_install = true
+deps =
+    isort
+    flake8
 commands =
     isort --check-only --diff {toxinidir}/src {toxinidir}/setup.py
     flake8 src setup.py
-    check-manifest
-    check-python-versions
-deps =
-    check-manifest
-    check-python-versions >= 0.19.1
-    wheel
-    flake8
-    isort
 
 [testenv:isort-apply]
 basepython = python3

zope.proxy-5.1/appveyor.yml

@@ -1,49 +0,0 @@
-# Generated from:
-# https://github.com/zopefoundation/meta/tree/master/config/c-code
-environment:
-  # Currently the builds use @mgedmin's Appveyor account.  The PyPI token belongs
-  # to zope.wheelbuilder, which is managed by @mgedmin and @dataflake.
-  global:
-     TWINE_USERNAME: __token__
-     TWINE_PASSWORD:
-         secure: aoZC/+rvJKg8B5GMGIxd1bg9UDShk28EhfPQFKI9zy7kzygdgj0XuaK619sLe3s4B08bIJaIUAThxEvWq13IvdLb5Oyk8B9qubd+NnDiNuw8WCGy4owYnbl+61fUVVKJIf1ETQyGDooYrEuBo798/+ycQbilTpmncAHZb2KyZkmA210fcWr7OhwmlRtC4IiW7GPCaxU6qhzLlP5pnS2Tl+yy/qx2DiW2fKWqUqynrb1ZMsk6ygN4qV72glTY6wV0eYboAGlghrws1x5+Z10Yug==
-
-  matrix:
-    - python: 37-x64
-    - python: 38-x64
-    - python: 39-x64
-    - python: 310-x64
-    - python: 311-x64
-    - python: 312-x64
-
-install:
-  - "SET PYTHONVERSION=%PYTHON%"
-  - "SET PATH=C:\\Python%PYTHON%;c:\\Python%PYTHON%\\scripts;%PATH%"
-  - ps: |
-      $env:PYTHON = "C:\\Python${env:PYTHON}"
-      if (-not (Test-Path $env:PYTHON)) {
-        curl -o install_python.ps1 https://raw.githubusercontent.com/matthew-brett/multibuild/11a389d78892cf90addac8f69433d5e22bfa422a/install_python.ps1
-        .\install_python.ps1
-      }
-  - ps: if (-not (Test-Path $env:PYTHON)) { throw "No $env:PYTHON" }
-  - echo "C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /x64 > "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64\vcvars64.bat"
-  - python -m pip install -U pip
-  - pip install -U setuptools wheel
-  - pip install -U -e .[test]
-
-matrix:
-  fast_finish: true
-
-build_script:
-  - python -W ignore setup.py -q bdist_wheel
-
-test_script:
-  - zope-testrunner --test-path=src
-artifacts:
-  - path: 'dist\*.whl'
-    name: wheel
-
-deploy_script:
-  - ps: if ($env:APPVEYOR_REPO_TAG -eq $TRUE) { pip install twine; twine upload --skip-existing dist\*.whl }
-
-deploy: on

zope.proxy-5.1/docs/_build/doctest/output.txt

@@ -1,25 +0,0 @@
-Results of doctest builder run on 2023-10-05 12:40:24
-=====================================================
-
-Document: narr
---------------
-1 items passed all tests:
-  37 tests in default
-37 tests in 1 items.
-37 passed and 0 failed.
-Test passed.
-
-Document: api
--------------
-1 items passed all tests:
-  23 tests in default
-23 tests in 1 items.
-23 passed and 0 failed.
-Test passed.
-
-Doctest summary
-===============
-   60 tests
-    0 failures in tests
-    0 failures in setup code
-    0 failures in cleanup code

zope.proxy-5.1/docs/_build/html/_sources/api.rst.txt

@@ -1,95 +0,0 @@
-:mod:`zope.proxy` API
-=====================
-
-:mod:`zope.proxy.interfaces`
-----------------------------
-
-.. automodule:: zope.proxy.interfaces
-
-  .. autointerface:: IProxyIntrospection
-     :members:
-     :member-order: bysource
-
-
-:mod:`zope.proxy`
------------------
-
-.. automodule:: zope.proxy
-   :members:
-
-
-:mod:`zope.proxy.decorator`
----------------------------
-
-.. automodule:: zope.proxy.decorator
-
-   .. doctest::
-
-      >>> from zope.interface import Interface
-      >>> from zope.interface import directlyProvides
-      >>> from zope.interface import implementer
-      >>> class I1(Interface):
-      ...     pass
-      >>> class I2(Interface):
-      ...     pass
-      >>> class I3(Interface):
-      ...     pass
-      >>> class I4(Interface):
-      ...     pass
-      >>> from zope.proxy.decorator import SpecificationDecoratorBase
-      >>> @implementer(I1)
-      ... class D1(SpecificationDecoratorBase):
-      ...   pass
-      >>> @implementer(I2)
-      ... class D2(SpecificationDecoratorBase):
-      ...   pass
-      >>> @implementer(I3)
-      ... class X(object):
-      ...   pass
-      >>> x = X()
-      >>> directlyProvides(x, I4)
-
-   Interfaces of X are ordered with the directly-provided interfaces first.
-
-   .. doctest::
-
-      >>> from zope.interface import providedBy
-      >>> [interface.getName() for interface in list(providedBy(x))]
-      ['I4', 'I3']
-
-   When we decorate objects, what order should the interfaces come
-   in?  One could argue that decorators are less specific, so they
-   should come last.
-
-   .. doctest::
-
-      >>> [interface.getName() for interface in list(providedBy(D1(x)))]
-      ['I4', 'I3', 'I1']
-
-      >>> [interface.getName() for interface in list(providedBy(D2(D1(x))))]
-      ['I4', 'I3', 'I1', 'I2']
-
-   SpecificationDecorators also work with old-style classes:
-
-   .. doctest::
-
-      >>> @implementer(I3)
-      ... class X:
-      ...   pass
-
-      >>> x = X()
-      >>> directlyProvides(x, I4)
-
-      >>> [interface.getName() for interface in list(providedBy(x))]
-      ['I4', 'I3']
-
-      >>> [interface.getName() for interface in list(providedBy(D1(x)))]
-      ['I4', 'I3', 'I1']
-
-      >>> [interface.getName() for interface in list(providedBy(D2(D1(x))))]
-      ['I4', 'I3', 'I1', 'I2']
-
-   .. autoclass:: DecoratorSpecificationDescriptor
-      :members:
-
-   .. autoclass:: SpecificationDecoratorBase

zope.proxy-5.1/docs/_build/html/_sources/changes.rst.txt

@@ -1 +0,0 @@
-.. include:: ../CHANGES.rst

zope.proxy-5.1/docs/_build/html/_sources/hacking.rst.txt

@@ -1,311 +0,0 @@
-Hacking on :mod:`zope.proxy`
-============================
-
-
-Getting the Code
-################
-
-The main repository for :mod:`zope.proxy` is in the Zope Foundation
-Github repository:
-
-  https://github.com/zopefoundation/zope.proxy
-
-You can get a read-only checkout from there:
-
-.. code-block:: sh
-
-   $ git clone https://github.com/zopefoundation/zope.proxy.git
-
-or fork it and get a writeable checkout of your fork:
-
-.. code-block:: sh
-
-   $ git clone git@github.com/jrandom/zope.proxy.git
-
-The project also mirrors the trunk from the Github repository as a
-Bazaar branch on Launchpad:
-
-https://code.launchpad.net/zope.proxy
-
-You can branch the trunk from there using Bazaar:
-
-.. code-block:: sh
-
-   $ bzr branch lp:zope.proxy
-
-
-Working in a ``virtualenv``
-###########################
-
-Installing
-----------
-
-If you use the ``virtualenv`` package to create lightweight Python
-development environments, you can run the tests using nothing more
-than the ``python`` binary in a virtualenv.  First, create a scratch
-environment:
-
-.. code-block:: sh
-
-   $ /path/to/virtualenv --no-site-packages /tmp/hack-zope.proxy
-
-Next, get this package registered as a "development egg" in the
-environment:
-
-.. code-block:: sh
-
-   $ /tmp/hack-zope.proxy/bin/python setup.py develop
-
-Running the tests
------------------
-
-Then, you canrun the tests using the build-in ``setuptools`` testrunner:
-
-.. code-block:: sh
-
-   $ /tmp/hack-zope.proxy/bin/python setup.py test -q
-   ...................................................................................................................................................
-   ----------------------------------------------------------------------
-   Ran 147 tests in 0.010s
-   
-   OK
-   
-
-If you have the :mod:`nose` package installed in the virtualenv, you can
-use its testrunner too:
-
-.. code-block:: sh
-
-   $ /tmp/hack-zope.proxy/bin/easy_install nose
-   ...
-   $ /tmp/hack-zope.proxy/bin/nosetests
-   .....................................................................................................................................................
-   ----------------------------------------------------------------------
-   Ran 149 tests in 0.107s
-   
-   OK
-
-If you have the :mod:`coverage` pacakge installed in the virtualenv,
-you can see how well the tests cover the code:
-
-.. code-block:: sh
-
-   $ /tmp/hack-zope.proxy/bin/easy_install nose coverage
-   ...
-   $ /tmp/hack-zope.proxy/bin/nosetests --with coverage
-   .....................................................................................................................................................
-   Name                    Stmts   Miss  Cover   Missing
-   -----------------------------------------------------
-   zope.proxy                271      0   100%   
-   zope.proxy._compat          2      0   100%   
-   zope.proxy.decorator       18      0   100%   
-   zope.proxy.interfaces      10      0   100%   
-   -----------------------------------------------------
-   TOTAL                     301      0   100%   
-   ----------------------------------------------------------------------
-   Ran 149 tests in 0.148s
-   
-   OK
-
-
-Building the documentation
---------------------------
-
-:mod:`zope.proxy` uses the nifty :mod:`Sphinx` documentation system
-for building its docs.  Using the same virtualenv you set up to run the
-tests, you can build the docs:
-
-.. code-block:: sh
-
-   $ /tmp/hack-zope.proxy/bin/easy_install Sphinx
-   ...
-   $ cd docs
-   $ /tmp/hack-zope.proxy/bin/sphinx-build \
-     -b html -d _build/doctrees   . _build/html
-   ...
-   build succeeded.
-
-You can also test the code snippets in the documentation:
-
-.. code-block:: sh
-
-   $ /tmp/hack-zope.proxy/bin/sphinx-build \
-    -b doctest -d _build/doctrees   . _build/doctest
-   ...
-   running tests...
-
-   Document: api
-   -------------
-   1 items passed all tests:
-     23 tests in default
-   23 tests in 1 items.
-   23 passed and 0 failed.
-   Test passed.
-
-   Document: narr
-   --------------
-   1 items passed all tests:
-     37 tests in default
-   37 tests in 1 items.
-   37 passed and 0 failed.
-   Test passed.
-
-   Doctest summary
-   ===============
-      60 tests
-       0 failures in tests
-       0 failures in setup code
-       0 failures in cleanup code
-   build succeeded.
-
-
-
-Using :mod:`zc.buildout`
-########################
-
-Setting up the buildout
------------------------
-
-:mod:`zope.proxy` ships with its own :file:`buildout.cfg` file and
-:file:`bootstrap.py` for setting up a development buildout:
-
-.. code-block:: sh
-
-   $ /path/to/python2.6 bootstrap.py
-   ...
-   Generated script '.../bin/buildout'
-   $ bin/buildout
-   Develop: '/home/jrandom/projects/Zope/BTK/event/.'
-   ...
-   Generated script '.../bin/test'.
-
-Running the tests
------------------
-
-You can now run the tests:
-
-.. code-block:: sh
-
-   $ bin/test --all
-   Running zope.testing.testrunner.layer.UnitTests tests:
-     Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
-     Ran 147 tests with 0 failures and 0 errors in 0.000 seconds.
-   Tearing down left over layers:
-     Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
-
-
-
-Using :mod:`tox`
-################
-
-Running Tests on Multiple Python Versions
------------------------------------------
-
-`tox <http://tox.testrun.org/latest/>`_ is a Python-based test automation
-tool designed to run tests against multiple Python versions.  It creates
-a ``virtualenv`` for each configured version, installs the current package
-and configured dependencies into each ``virtualenv``, and then runs the
-configured commands.
-   
-:mod:`zope.proxy` configures the following :mod:`tox` environments via
-its ``tox.ini`` file:
-
-- The ``py26``, ``py27``, ``py33``, ``py34``, and ``pypy`` environments
-  builds a ``virtualenv`` with ``pypy``,
-  installs :mod:`zope.proxy` and dependencies, and runs the tests
-  via ``python setup.py test -q``.
-
-- The ``coverage`` environment builds a ``virtualenv`` with ``python2.6``,
-  installs :mod:`zope.proxy`, installs
-  :mod:`nose` and :mod:`coverage`, and runs ``nosetests`` with statement
-  coverage.
-
-- The ``docs`` environment builds a virtualenv with ``python2.6``, installs
-  :mod:`zope.proxy`, installs ``Sphinx`` and
-  dependencies, and then builds the docs and exercises the doctest snippets.
-
-This example requires that you have a working ``python2.6`` on your path,
-as well as installing ``tox``:
-
-.. code-block:: sh
-
-   $ tox -e py26
-   GLOB sdist-make: .../zope.proxy/setup.py
-   py26 sdist-reinst: .../zope.proxy/.tox/dist/zope.proxy-4.0.2dev.zip
-   py26 runtests: commands[0]
-   ...
-   ----------------------------------------------------------------------
-   Ran 147 tests in 0.000s
-
-   OK
-   ___________________________________ summary ____________________________________
-   py26: commands succeeded
-   congratulations :)
-
-Running ``tox`` with no arguments runs all the configured environments,
-including building the docs and testing their snippets:
-
-.. code-block:: sh
-
-   $ tox
-   GLOB sdist-make: .../zope.proxy/setup.py
-   py26 sdist-reinst: .../zope.proxy/.tox/dist/zope.proxy-4.0.2dev.zip
-   py26 runtests: commands[0]
-   ...
-   Doctest summary
-   ===============
-    60 tests
-      0 failures in tests
-      0 failures in setup code
-      0 failures in cleanup code
-   build succeeded.
-   ___________________________________ summary ____________________________________
-   py26: commands succeeded
-   py27: commands succeeded
-   py32: commands succeeded
-   pypy: commands succeeded
-   coverage: commands succeeded
-   docs: commands succeeded
-   congratulations :)
-
-
-Contributing to :mod:`zope.proxy`
-#################################
-
-Submitting a Bug Report
------------------------
-
-:mod:`zope.proxy` tracks its bugs on Github:
-
-  https://github.com/zopefoundation/zope.proxy/issues
-
-Please submit bug reports and feature requests there.
-
-
-Sharing Your Changes
---------------------
-
-.. note::
-
-   Please ensure that all tests are passing before you submit your code.
-   If possible, your submission should include new tests for new features
-   or bug fixes, although it is possible that you may have tested your
-   new code by updating existing tests.
-
-If have made a change you would like to share, the best route is to fork
-the Githb repository, check out your fork, make your changes on a branch
-in your fork, and push it.  You can then submit a pull request from your
-branch:
-
-  https://github.com/zopefoundation/zope.proxy/pulls
-
-If you branched the code from Launchpad using Bazaar, you have another
-option:  you can "push" your branch to Launchpad:
-
-.. code-block:: sh
-
-   $ bzr push lp:~jrandom/zope.proxy/cool_feature
-
-After pushing your branch, you can link it to a bug report on Github,
-or request that the maintainers merge your branch using the Launchpad
-"merge request" feature.

zope.proxy-5.1/docs/_build/html/_sources/index.rst.txt

@@ -1,20 +0,0 @@
-:mod:`zope.proxy`
-=================
-
-Contents:
-
-.. toctree::
-   :maxdepth: 2
-
-   narr
-   api
-   hacking
-   changes
-
-
-Indices and tables
-==================
-
-* :ref:`genindex`
-* :ref:`modindex`
-* :ref:`search`

zope.proxy-5.1/docs/_build/html/_sources/narr.rst.txt

@@ -1,153 +0,0 @@
-:mod:`zope.proxy` Narrative Documentation
-=========================================
-
-Subclassing :class:`ProxyBase`
-------------------------------
-
-If you subclass a proxy, instances of the subclass have access to
-data defined in the class, including descriptors.
-
-Your subclass instances don't get instance dictionaries, but they
-can have slots.
-
-.. doctest::
-
-   >>> from zope.proxy import ProxyBase
-   >>> class MyProxy(ProxyBase):
-   ...    __slots__ = 'x', 'y'
-   ...
-   ...    def f(self):
-   ...        return self.x
-
-   >>> l = [1, 2, 3]
-   >>> p = MyProxy(l)
-
-You can use attributes defined by the class, including slots:
-
-.. doctest::
-
-   >>> p.x = 'x'
-   >>> p.x
-   'x'
-   >>> p.f()
-   'x'
-
-You can also use attributes of the proxied object:
-
-.. doctest::
-
-   >>> p
-   [1, 2, 3]
-   >>> p.pop()
-   3
-   >>> p
-   [1, 2]
-
-
-Using get descriptors in proxy classes
---------------------------------------
-
-A non-data descriptor in a proxy class doesn't hide an attribute on
-a proxied object or prevent writing the attribute.
-
-.. doctest::
-
-    >>> class ReadDescr(object):
-    ...     def __get__(self, i, c):
-    ...         return 'read'
-
-    >>> from zope.proxy import ProxyBase
-    >>> class MyProxy(ProxyBase):
-    ...    __slots__ = ()
-    ...
-    ...    z = ReadDescr()
-    ...    q = ReadDescr()
-
-    >>> class MyOb:
-    ...    q = 1
-
-    >>> o = MyOb()
-    >>> p = MyProxy(o)
-    >>> p.q
-    1
-
-    >>> p.z
-    'read'
-
-    >>> p.z = 1
-    >>> o.z, p.z
-    (1, 1)
-
-
-Marking proxy attributes as non-overridable
--------------------------------------------
-
-Normally, methods defined in proxies are overridden by
-methods of proxied objects.  This applies to all non-data
-descriptors.  The non_overridable function can be used to
-convert a non-data descriptor to a data descriptor that disallows
-writes.  This function can be used as a decorator to make functions
-defined in proxy classes take precedence over functions defined
-in proxied objects.
-
-.. doctest::
-
-   >>> from zope.proxy import ProxyBase
-   >>> from zope.proxy import non_overridable
-   >>> class MyProxy(ProxyBase):
-   ...    __slots__ = ()
-   ...
-   ...    @non_overridable
-   ...    def foo(self):
-   ...        return 'MyProxy foo'
-
-   >>> class MyOb:
-   ...    def foo(self):
-   ...        return 'MyOb foo'
-
-   >>> o = MyOb()
-   >>> p = MyProxy(o)
-   >>> p.foo()
-   'MyProxy foo'
-
-
-Changing the proxied object
----------------------------
-
-.. doctest::
-
-   >>> from zope.proxy import ProxyBase
-   >>> from zope.proxy import setProxiedObject, getProxiedObject
-
-   >>> class C(object):
-   ...     pass
-
-   >>> c1 = C()
-   >>> c2 = C()
-
-   >>> p = ProxyBase(c1)
-
-`setProxiedObject()` allows us to change the object a proxy refers to,
-returning the previous referent:
-
-.. doctest::
-
-   >>> old = setProxiedObject(p, c2)
-   >>> old is c1
-   True
-
-   >>> getProxiedObject(p) is c2
-   True
-
-The first argument  to `setProxiedObject()` must be a proxy; other objects
-cause it to raise an exception:
-
-.. doctest::
-
-   >>> try:
-   ...     setProxiedObject(c1, None)
-   ... except TypeError:
-   ...     print("TypeError raised")
-   ... else:
-   ...     print("Expected TypeError not raised")
-   TypeError raised