Update documentation with PyPy compatability

Adds details of testing and compatability with PyPy to the README and
proejct documentation.
This commit is contained in:
Aaron Iles 2013-01-07 21:58:49 +11:00
parent c65d42f7da
commit 8ae3ff896f
2 changed files with 12 additions and 8 deletions

View File

@ -35,13 +35,15 @@ The ``funcsigs`` backport has been tested against:
* CPython 2.6
* CPython 2.7
* CPython 3.2
* PyPy 1.9
Continuous integration testing is provided by `Travis CI`_.
There is one known compatability issue with Python 2.x when a function is
assigned to the ``__wrapped__`` property of a class after it has been
constructed. Otherwise the functionality is believed to be uniform between both
Python2 and Python3.
Under Python 2.x there is a compatability issue when a function is assigned to
the ``__wrapped__`` property of a class after it has been constructed.
Similiarily there under PyPy directly passing the ``__call__`` method of a
builtin is also a compatability issues. Otherwise the functionality is
believed to be uniform between both Python2 and Python3.
Issues
------

View File

@ -24,13 +24,15 @@ The *funcsigs* backport has been tested against:
* CPython 2.6
* CPython 2.7
* CPython 3.2
* PyPy 1.9
Continuous integration testing is provided by `Travis CI`_.
There is one known compatability issue with Python 2.x when a function is
assigned to the ``__wrapped__`` property of a class after it has been
constructed. Otherwise the functionality is believed to be uniform between both
Python2 and Python3.
Under Python 2.x there is a compatability issue when a function is assigned to
the ``__wrapped__`` property of a class after it has been constructed.
Similiarily there under PyPy directly passing the ``__call__`` method of a
builtin is also a compatability issues. Otherwise the functionality is
believed to be uniform between both Python2 and Python3.
.. _Travis CI: http://travis-ci.org/