Commit 9a1ac7a4 authored by Armin Rigo's avatar Armin Rigo

transplant 7cb52d2a97f0

parent 71ecc360
......@@ -740,7 +740,7 @@ it is executed.
Adding an entry under pypy/module (e.g. mymodule) entails automatic
creation of a new config option (such as --withmod-mymodule and
--withoutmod-mymodule (the later being the default)) for py.py and
--withoutmod-mymodule (the latter being the default)) for py.py and
translate.py.
Testing modules in ``lib_pypy/``
......@@ -931,7 +931,7 @@ Another possibility is to use cls.space.appexec, for example::
assert self.result == 2 ** 6
which executes the code string function with the given arguments at app level.
Note the use of ``w_result`` in ``setup_class`` but self.result in the test
Note the use of ``w_result`` in ``setup_class`` but self.result in the test.
Here is how to define an app level class in ``setup_class`` that can be used
in subsequent tests::
......
......@@ -328,7 +328,7 @@ Miscellaneous
* directly calling the internal magic methods of a few built-in types
with invalid arguments may have a slightly different result. For
example, ``[].__add__(None)`` and ``(2).__add__(None)`` both return
``NotImplemented`` on PyPy; on CPython, only the later does, and the
``NotImplemented`` on PyPy; on CPython, only the latter does, and the
former raises ``TypeError``. (Of course, ``[]+None`` and ``2+None``
both raise ``TypeError`` everywhere.) This difference is an
implementation detail that shows up because of internal C-level slots
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment