Addition of 'open issues' to PEP 417

This commit is contained in:
Michael Foord 2012-03-12 15:13:48 -07:00
parent 7404685a67
commit f02b024aa0
1 changed files with 16 additions and 4 deletions

View File

@ -13,7 +13,7 @@ Post-History: 12-Mar-2012
Abstract
This PEP proposes adding the mock [1]_ testing library
This PEP proposes adding the mock [1] testing library
to the Python standard library as ``unittest.mock``.
@ -24,7 +24,7 @@ Rationale
suites. This is currently what we do in the Python test suite,
where a standardised mock object library would be helpful.
There are many mock object libraries available for Python [2]_.
There are many mock object libraries available for Python [2].
Of these, mock is overwhelmingly the most popular, with as many
downloads on PyPI as the other mocking libraries combined.
@ -38,7 +38,7 @@ Rationale
and many developers / projects mimic this functionality
(often incorrectly). A standardised way to do this, handling
the complexity of patching in the presence of the descriptor
protocol (etc) is useful. People are asking for a "patch" [3]_
protocol (etc) is useful. People are asking for a "patch" [3]
feature to unittest. Doing this via mock.patch is preferable
to re-implementing part of this functionality in unittest.
@ -46,11 +46,23 @@ Rationale
Background
Addition of mock to the Python standard library was discussed
and agreed to at the Python Language Summit 2012.
Open Issues
As of release 0.8, which is current at the time of writing,
mock is compatible with Python 2.4-3.2. Moving into the Python
standard library will allow for the removal of some Python 2
specific "compatibility hacks".
mock 0.8 introduced a new feature, "auto-speccing", obsoletes
an older mock feature called "mocksignature". The
"mocksignature" functionality can be removed from mock
altogether prior to inclusion.
References
[1] `mock library on PyPI<http://pypi.python.org/pypi/mock>`_
[1] `mock library on PyPI <http://pypi.python.org/pypi/mock>`_
[2] http://pypi.python.org/pypi?%3Aaction=search&term=mock&submit=search
[3] http://bugs.python.org/issue11664