PEP 510: rephrase introduction on PyPy
suggestion of Yury Selivanov
This commit is contained in:
parent
62cad3ab0c
commit
cb2695ed1f
|
@ -55,10 +55,11 @@ There are multiple JIT compilers for Python actively developed:
|
|||
* `Pyjion <https://github.com/microsoft/pyjion>`_
|
||||
|
||||
Numba is specific to numerical computation. Pyston and Pyjion are still
|
||||
young. PyPy is the most complete Python interpreter, it is much faster
|
||||
than CPython and has a very good compatibility with CPython (it respects
|
||||
the Python semantics). There are still issues with Python JIT compilers
|
||||
which avoid them to be widely used instead of CPython.
|
||||
young. PyPy is the most complete Python interpreter, it is generally
|
||||
faster than CPython in micro- and many macro-benchmarks and has a very
|
||||
good compatibility with CPython (it respects the Python semantics).
|
||||
There are still issues with Python JIT compilers which avoid them to be
|
||||
widely used instead of CPython.
|
||||
|
||||
Many popular libraries like numpy, PyGTK, PyQt, PySide and wxPython are
|
||||
implemented in C or C++ and use the Python C API. To have a small memory
|
||||
|
|
Loading…
Reference in New Issue