Update documentation with PyPy compatability
Adds details of testing and compatability with PyPy to the README and
proejct documentation.
diff --git a/README.rst b/README.rst
index 328abb3..ed76f16 100644
--- a/README.rst
+++ b/README.rst
@@ -35,13 +35,15 @@
* 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
------
diff --git a/docs/index.rst b/docs/index.rst
index e7da6c2..5d0f42f 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -24,13 +24,15 @@
* 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/
