# PyPy 4.0.1

We have released PyPy 4.0.1, three weeks after PyPy 4.0.0. We have fixed a few critical bugs in the JIT compiled code, reported by users. We therefore encourage all users of PyPy to update to this version. There are a few minor enhancements in this version as well.

You can download the PyPy 4.0.1 release here:

> http://pypy.org/download.html

We would like to thank our donors for the continued support of the PyPy project.

We would also like to thank our contributors and encourage new people to join the project. PyPy has many layers and we need help with all of them: PyPy and RPython documentation improvements, tweaking popular modules to run on pypy, or general help with making RPython’s JIT even better.

## CFFI

While not applicable only to PyPy, cffi is arguably our most significant contribution to the python ecosystem. PyPy 4.0.1 ships with cffi-1.3.1 with the improvements it brings.

## What is PyPy?

PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython 2.7. It’s fast (pypy and cpython 2.7.x performance comparison) due to its integrated tracing JIT compiler.

We also welcome developers of other dynamic languages to see what RPython can do for them.

This release supports x86 machines on most common operating systems (Linux 32/64, Mac OS X 64, Windows 32, OpenBSD, freebsd), newer ARM hardware (ARMv6 or ARMv7, with VFPv3) running Linux, and the big- and little-endian variants of ppc64 running Linux.

## Other Highlights (since 4.0.0 released three weeks ago)

- Bug Fixes
  - Fix a bug when unrolling double loops in JITted code
  - Fix multiple memory leaks in the ssl module, one of which affected cpython as well (thanks to Alex Gaynor for pointing those out)
  - Use pkg-config to find ssl headers on OS-X
  - Issues reported with our previous release were resolved after reports from users on our issue tracker at https://bitbucket.org/pypy/pypy/issues or on IRC at #pypy
- New features:
  - Internal cleanup of RPython class handling
  - Support stackless and greenlets on PPC machines
  - Improve debug logging in subprocesses: use PYPYLOG=jit:log.%d for example to have all subprocesses write the JIT log to a file called ‘log.%d’, with ‘%d’ replaced with the subprocess’ PID.
  - Support PyOS_double_to_string in our cpyext capi compatibility layer
- Numpy:
  - Improve support for __array_interface__
  - Propagate NAN mantissas through float16-float32-float64 conversions
- Performance improvements and refactorings:
  - Improvements in slicing byte arrays
  - Improvements in enumerate()
  - Silence some warnings while translating

Please update, and continue to help us make PyPy better.

Cheers

The PyPy Team