[pypy-dev] PyPy3 2.4.0 released

[Phyo Arkar]

Congrats!
I am using Pypy 2.4 for tornado based web development , performance
improvement is the real deal there.

i am waiting to switch to python3 and its becoming near! Its when
pypy3 3.4 is ready (ie , Python3 is only starting to interesting after
3.4.x due to asyncio module) .

I have a question:
In CPython , python 2 vs python 3 is around 10-30% performance
difference. In PyPy world is there such difference? Same performance
between pypy2 and pypy3 ?


On Tue, Oct 21, 2014 at 11:32 PM, Philip Jenvey <pjenvey at underboss.org> wrote:
> =================================================
> PyPy3 2.4 - Snow White
> =================================================
>
> We're pleased to announce PyPy3 2.4, which contains significant performance
> enhancements and bug fixes.
>
> You can download the PyPy3 2.4.0 release here:
>
>     http://pypy.org/download.html
>
> PyPy3 Highlights
> ================
>
> Issues reported with our previous release were fixed after reports from users on
> our new issue tracker at https://bitbucket.org/pypy/pypy/issues or on IRC at
> #pypy. Here is a summary of the user-facing PyPy3 specific changes:
>
> * Better Windows compatibility, e.g. the nt module functions _getfinalpathname
>   & _getfileinformation are now supported (the former is required for the
>   popular pathlib library for example)
>
> * Various fsencode PEP 383 related fixes to the posix module (readlink, uname,
>   ttyname and ctermid) and improved locale handling
>
> * Switched default binary name os POSIX distributions to 'pypy3' (which
>   symlinks to to 'pypy3.2')
>
> * Fixed a couple different crashes related to parsing Python 3 source code
>
> Further Highlights (shared w/ PyPy2)
> ====================================
>
> Benchmarks improved after internal enhancements in string and
> bytearray handling, and a major rewrite of the GIL handling. This means
> that external calls are now a lot faster, especially the CFFI ones. It also
> means better performance in a lot of corner cases with handling strings or
> bytearrays. The main bugfix is handling of many socket objects in your
> program which in the long run used to "leak" memory.
>
> We fixed a memory leak in IO in the sandbox_ code
>
> We welcomed more than 12 new contributors, and conducted two Google
> Summer of Code projects, as well as other student projects not
> directly related to Summer of Code.
>
> * Reduced internal copying of bytearray operations
>
> * Tweak the internal structure of StringBuilder to speed up large string
>   handling, which becomes advantageous on large programs at the cost of slightly
>   slower small *benchmark* type programs.
>
> * Boost performance of thread-local variables in both unjitted and jitted code,
>   this mostly affects errno handling on linux, which makes external calls
>   faster.
>
> * Move to a mixed polling and mutex GIL model that make mutlithreaded jitted
>   code run *much* faster
>
> * Optimize errno handling in linux (x86 and x86-64 only)
>
> * Remove ctypes pythonapi and ctypes.PyDLL, which never worked on PyPy
>
> * Classes in the ast module are now distinct from structures used by
>   the compiler, which simplifies and speeds up translation of our
>   source code to the PyPy binary interpreter
>
> * Win32 now links statically to zlib, expat, bzip, and openssl-1.0.1i.
>   No more missing DLLs
>
> * Many issues were resolved_ since the 2.3.1 release in June
>
> .. _`whats-new`: http://doc.pypy.org/en/latest/whatsnew-2.4.0.html
> .. _resolved: https://bitbucket.org/pypy/pypy/issues?status=resolved
> .. _sandbox: http://doc.pypy.org/en/latest/sandbox.html
>
> We have further improvements on the way: rpython file handling,
> numpy linalg compatibility, as well
> as improved GC and many smaller improvements.
>
> Please try it out and let us know what you think. We especially welcome
> success stories, we know you are using PyPy, please tell us about it!
>
> Cheers
>
> The PyPy Team
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev