PyPy 2.0 - Einstein Sandwich
We're pleased to announce PyPy 2.0. This is a stable release that brings a swath of bugfixes, small performance improvements and compatibility fixes. PyPy 2.0 is a big step for us and we hope in the future we'll be able to provide stable releases more often. You can download the PyPy 2.0 release here: http://pypy.org/download.html The two biggest changes since PyPy 1.9 are: * stackless is now supported including greenlets, which means eventlet and gevent should work (but read below about gevent) * PyPy now contains release 0.6 of `cffi`_ as a builtin module, which is preferred way of calling C from Python that works well on PyPy .. _`cffi`: http://cffi.readthedocs.org If you're using PyPy for anything, it would help us immensely if you fill out the following survey: http://bit.ly/pypysurvey This is for the developers eyes and we will not make any information public without your agreement. What is PyPy? ============= PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython 2.7. It's fast (`pypy 2.0 and cpython 2.7.3`_ performance comparison) due to its integrated tracing JIT compiler. This release supports x86 machines running Linux 32/64, Mac OS X 64 or Windows 32. Windows 64 work is still stalling, we would welcome a volunteer to handle that. ARM support is on the way, as you can see from the recently released alpha for ARM. .. _`pypy 2.0 and cpython 2.7.3`: http://speed.pypy.org Highlights ========== * Stackless including greenlets should work. For gevent, you need to check out `pypycore`_ and use the `pypy-hacks`_ branch of gevent. * cffi is now a module included with PyPy. (`cffi`_ also exists for CPython; the two versions should be fully compatible.) It is the preferred way of calling C from Python that works on PyPy. * Callbacks from C are now JITted, which means XML parsing is much faster. * A lot of speed improvements in various language corners, most of them small, but speeding up some particular corners a lot. * The JIT was refactored to emit machine code which manipulates a "frame" that lives on the heap rather than on the stack. This is what makes Stackless work, and it could bring another future speed-up (not done yet). * A lot of stability issues fixed. * Refactoring much of the numpypy array classes, which resulted in removal of lazy expression evaluation. On the other hand, we now have more complete dtype support and support more array attributes. .. _`pypycore`: https://github.com/gevent-on-pypy/pypycore/ .. _`pypy-hacks`: https://github.com/schmir/gevent/tree/pypy-hacks Cheers, fijal, arigo and the PyPy team
Hi Maciej! * Callbacks from C are now JITted, which means XML parsing is much faster. You mean, cffi callbacks? regards, 2013/5/9 Maciej Fijalkowski <fijall@gmail.com>
We're pleased to announce PyPy 2.0. This is a stable release that brings a swath of bugfixes, small performance improvements and compatibility fixes. PyPy 2.0 is a big step for us and we hope in the future we'll be able to provide stable releases more often.
You can download the PyPy 2.0 release here:
The two biggest changes since PyPy 1.9 are:
* stackless is now supported including greenlets, which means eventlet and gevent should work (but read below about gevent)
* PyPy now contains release 0.6 of `cffi`_ as a builtin module, which is preferred way of calling C from Python that works well on PyPy
.. _`cffi`: http://cffi.readthedocs.org
If you're using PyPy for anything, it would help us immensely if you fill out the following survey: http://bit.ly/pypysurvey This is for the developers eyes and we will not make any information public without your agreement.
What is PyPy? =============
PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython 2.7. It's fast (`pypy 2.0 and cpython 2.7.3`_ performance comparison) due to its integrated tracing JIT compiler.
This release supports x86 machines running Linux 32/64, Mac OS X 64 or Windows 32. Windows 64 work is still stalling, we would welcome a volunteer to handle that. ARM support is on the way, as you can see from the recently released alpha for ARM.
.. _`pypy 2.0 and cpython 2.7.3`: http://speed.pypy.org
Highlights ==========
* Stackless including greenlets should work. For gevent, you need to check out `pypycore`_ and use the `pypy-hacks`_ branch of gevent.
* cffi is now a module included with PyPy. (`cffi`_ also exists for CPython; the two versions should be fully compatible.) It is the preferred way of calling C from Python that works on PyPy.
* Callbacks from C are now JITted, which means XML parsing is much faster.
* A lot of speed improvements in various language corners, most of them small, but speeding up some particular corners a lot.
* The JIT was refactored to emit machine code which manipulates a "frame" that lives on the heap rather than on the stack. This is what makes Stackless work, and it could bring another future speed-up (not done yet).
* A lot of stability issues fixed.
* Refactoring much of the numpypy array classes, which resulted in removal of lazy expression evaluation. On the other hand, we now have more complete dtype support and support more array attributes.
.. _`pypycore`: https://github.com/gevent-on-pypy/pypycore/ .. _`pypy-hacks`: https://github.com/schmir/gevent/tree/pypy-hacks
Cheers, fijal, arigo and the PyPy team _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
-- Felipe Cruz http://about.me/felipecruz
cffi callbacks, as well as those in RPython (like those used by expat) Alex On Thu, May 9, 2013 at 2:15 PM, Felipe Cruz <felipecruz@loogica.net> wrote:
Hi Maciej!
* Callbacks from C are now JITted, which means XML parsing is much faster.
You mean, cffi callbacks?
regards,
2013/5/9 Maciej Fijalkowski <fijall@gmail.com>
We're pleased to announce PyPy 2.0. This is a stable release that brings a swath of bugfixes, small performance improvements and compatibility fixes. PyPy 2.0 is a big step for us and we hope in the future we'll be able to provide stable releases more often.
You can download the PyPy 2.0 release here:
The two biggest changes since PyPy 1.9 are:
* stackless is now supported including greenlets, which means eventlet and gevent should work (but read below about gevent)
* PyPy now contains release 0.6 of `cffi`_ as a builtin module, which is preferred way of calling C from Python that works well on PyPy
.. _`cffi`: http://cffi.readthedocs.org
If you're using PyPy for anything, it would help us immensely if you fill out the following survey: http://bit.ly/pypysurvey This is for the developers eyes and we will not make any information public without your agreement.
What is PyPy? =============
PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython 2.7. It's fast (`pypy 2.0 and cpython 2.7.3`_ performance comparison) due to its integrated tracing JIT compiler.
This release supports x86 machines running Linux 32/64, Mac OS X 64 or Windows 32. Windows 64 work is still stalling, we would welcome a volunteer to handle that. ARM support is on the way, as you can see from the recently released alpha for ARM.
.. _`pypy 2.0 and cpython 2.7.3`: http://speed.pypy.org
Highlights ==========
* Stackless including greenlets should work. For gevent, you need to check out `pypycore`_ and use the `pypy-hacks`_ branch of gevent.
* cffi is now a module included with PyPy. (`cffi`_ also exists for CPython; the two versions should be fully compatible.) It is the preferred way of calling C from Python that works on PyPy.
* Callbacks from C are now JITted, which means XML parsing is much faster.
* A lot of speed improvements in various language corners, most of them small, but speeding up some particular corners a lot.
* The JIT was refactored to emit machine code which manipulates a "frame" that lives on the heap rather than on the stack. This is what makes Stackless work, and it could bring another future speed-up (not done yet).
* A lot of stability issues fixed.
* Refactoring much of the numpypy array classes, which resulted in removal of lazy expression evaluation. On the other hand, we now have more complete dtype support and support more array attributes.
.. _`pypycore`: https://github.com/gevent-on-pypy/pypycore/ .. _`pypy-hacks`: https://github.com/schmir/gevent/tree/pypy-hacks
Cheers, fijal, arigo and the PyPy team _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
-- Felipe Cruz http://about.me/felipecruz
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
-- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: 125F 5C67 DFE9 4084
Thanks Alex! great news! crongrats all! 2013/5/9 Alex Gaynor <alex.gaynor@gmail.com>
cffi callbacks, as well as those in RPython (like those used by expat)
Alex
On Thu, May 9, 2013 at 2:15 PM, Felipe Cruz <felipecruz@loogica.net>wrote:
Hi Maciej!
* Callbacks from C are now JITted, which means XML parsing is much faster.
You mean, cffi callbacks?
regards,
2013/5/9 Maciej Fijalkowski <fijall@gmail.com>
We're pleased to announce PyPy 2.0. This is a stable release that brings a swath of bugfixes, small performance improvements and compatibility fixes. PyPy 2.0 is a big step for us and we hope in the future we'll be able to provide stable releases more often.
You can download the PyPy 2.0 release here:
The two biggest changes since PyPy 1.9 are:
* stackless is now supported including greenlets, which means eventlet and gevent should work (but read below about gevent)
* PyPy now contains release 0.6 of `cffi`_ as a builtin module, which is preferred way of calling C from Python that works well on PyPy
.. _`cffi`: http://cffi.readthedocs.org
If you're using PyPy for anything, it would help us immensely if you fill out the following survey: http://bit.ly/pypysurvey This is for the developers eyes and we will not make any information public without your agreement.
What is PyPy? =============
PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython 2.7. It's fast (`pypy 2.0 and cpython 2.7.3`_ performance comparison) due to its integrated tracing JIT compiler.
This release supports x86 machines running Linux 32/64, Mac OS X 64 or Windows 32. Windows 64 work is still stalling, we would welcome a volunteer to handle that. ARM support is on the way, as you can see from the recently released alpha for ARM.
.. _`pypy 2.0 and cpython 2.7.3`: http://speed.pypy.org
Highlights ==========
* Stackless including greenlets should work. For gevent, you need to check out `pypycore`_ and use the `pypy-hacks`_ branch of gevent.
* cffi is now a module included with PyPy. (`cffi`_ also exists for CPython; the two versions should be fully compatible.) It is the preferred way of calling C from Python that works on PyPy.
* Callbacks from C are now JITted, which means XML parsing is much faster.
* A lot of speed improvements in various language corners, most of them small, but speeding up some particular corners a lot.
* The JIT was refactored to emit machine code which manipulates a "frame" that lives on the heap rather than on the stack. This is what makes Stackless work, and it could bring another future speed-up (not done yet).
* A lot of stability issues fixed.
* Refactoring much of the numpypy array classes, which resulted in removal of lazy expression evaluation. On the other hand, we now have more complete dtype support and support more array attributes.
.. _`pypycore`: https://github.com/gevent-on-pypy/pypycore/ .. _`pypy-hacks`: https://github.com/schmir/gevent/tree/pypy-hacks
Cheers, fijal, arigo and the PyPy team _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
-- Felipe Cruz http://about.me/felipecruz
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
-- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: 125F 5C67 DFE9 4084
-- Felipe Cruz http://about.me/felipecruz
Good news. Unfortunately there is a dependency on libtinfo.so : ./bin/pypy: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory On Fri, May 10, 2013 at 1:09 AM, Maciej Fijalkowski <fijall@gmail.com>wrote:
We're pleased to announce PyPy 2.0. This is a stable release that brings a swath of bugfixes, small performance improvements and compatibility fixes. PyPy 2.0 is a big step for us and we hope in the future we'll be able to provide stable releases more often.
You can download the PyPy 2.0 release here:
The two biggest changes since PyPy 1.9 are:
* stackless is now supported including greenlets, which means eventlet and gevent should work (but read below about gevent)
* PyPy now contains release 0.6 of `cffi`_ as a builtin module, which is preferred way of calling C from Python that works well on PyPy
.. _`cffi`: http://cffi.readthedocs.org
If you're using PyPy for anything, it would help us immensely if you fill out the following survey: http://bit.ly/pypysurvey This is for the developers eyes and we will not make any information public without your agreement.
What is PyPy? =============
PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython 2.7. It's fast (`pypy 2.0 and cpython 2.7.3`_ performance comparison) due to its integrated tracing JIT compiler.
This release supports x86 machines running Linux 32/64, Mac OS X 64 or Windows 32. Windows 64 work is still stalling, we would welcome a volunteer to handle that. ARM support is on the way, as you can see from the recently released alpha for ARM.
.. _`pypy 2.0 and cpython 2.7.3`: http://speed.pypy.org
Highlights ==========
* Stackless including greenlets should work. For gevent, you need to check out `pypycore`_ and use the `pypy-hacks`_ branch of gevent.
* cffi is now a module included with PyPy. (`cffi`_ also exists for CPython; the two versions should be fully compatible.) It is the preferred way of calling C from Python that works on PyPy.
* Callbacks from C are now JITted, which means XML parsing is much faster.
* A lot of speed improvements in various language corners, most of them small, but speeding up some particular corners a lot.
* The JIT was refactored to emit machine code which manipulates a "frame" that lives on the heap rather than on the stack. This is what makes Stackless work, and it could bring another future speed-up (not done yet).
* A lot of stability issues fixed.
* Refactoring much of the numpypy array classes, which resulted in removal of lazy expression evaluation. On the other hand, we now have more complete dtype support and support more array attributes.
.. _`pypycore`: https://github.com/gevent-on-pypy/pypycore/ .. _`pypy-hacks`: https://github.com/schmir/gevent/tree/pypy-hacks
Cheers, fijal, arigo and the PyPy team _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
2013/5/10 Phyo Arkar <phyo.arkarlwin@gmail.com>
Unfortunately there is a dependency on libtinfo.so :
./bin/pypy: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
Yes, this is certainly pulled by the _curses module. But this was also the case with pypy-1.9. On which system are you running? -- Amaury Forgeot d'Arc
Sabayon Linux64bit i am not sure i tested 1.9 on this laptop On May 10, 2013 8:37 PM, "Amaury Forgeot d'Arc" <amauryfa@gmail.com> wrote:
2013/5/10 Phyo Arkar <phyo.arkarlwin@gmail.com>
Unfortunately there is a dependency on libtinfo.so :
./bin/pypy: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
Yes, this is certainly pulled by the _curses module.
But this was also the case with pypy-1.9. On which system are you running?
-- Amaury Forgeot d'Arc
Phyo, On Fri, 10 May 2013, Phyo Arkar wrote:
./bin/pypy: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
not every distro splits up tinfo and ncurses. On SuSE, what I did was to provide a symlink libtinfo.so.5 -> libncurses.so and that satisfied the dependencies. Might be that that works on your system, too. Best regards, Wim -- WLavrijsen@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
Ah that's why i cannot find libtinfo.so thanks i will try that. On May 10, 2013 9:25 PM, <wlavrijsen@lbl.gov> wrote:
Phyo,
On Fri, 10 May 2013, Phyo Arkar wrote:
./bin/pypy: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
not every distro splits up tinfo and ncurses. On SuSE, what I did was to provide a symlink libtinfo.so.5 -> libncurses.so and that satisfied the dependencies. Might be that that works on your system, too.
Best regards, Wim -- WLavrijsen@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
just did that. got ELF header error @ /usr/lib64/libtinfo.so.5 On May 10, 2013 9:32 PM, "Phyo Arkar" <phyo.arkarlwin@gmail.com> wrote:
Ah that's why i cannot find libtinfo.so thanks i will try that. On May 10, 2013 9:25 PM, <wlavrijsen@lbl.gov> wrote:
Phyo,
On Fri, 10 May 2013, Phyo Arkar wrote:
./bin/pypy: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
not every distro splits up tinfo and ncurses. On SuSE, what I did was to provide a symlink libtinfo.so.5 -> libncurses.so and that satisfied the dependencies. Might be that that works on your system, too.
Best regards, Wim -- WLavrijsen@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
Phyo, On Fri, 10 May 2013, Phyo Arkar wrote:
just did that. got ELF header error @ /usr/lib64/libtinfo.so.5
what ELF header error? (Point being: pypy is linked with libncurses.so as well, so that library has to be correct to begin with.) Best regards, Wim -- WLavrijsen@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
Hi, On Fri, May 10, 2013 at 3:45 PM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:
./bin/pypy: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
The Linux binaries are provided for *32-bit Ubuntu 10.04* as well as *64-bit Ubuntu 12.04*. If you are not using exactly these versions, it won't work, likely, or you need to hack a lot --- or you need to translate your own version from source --- or you need to wait until your distribution adds a package. A bientôt, Armin.
it used to work fine before. its not problem i can build from source. On May 11, 2013 3:26 AM, "Armin Rigo" <arigo@tunes.org> wrote:
Hi,
On Fri, May 10, 2013 at 3:45 PM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:
./bin/pypy: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
The Linux binaries are provided for *32-bit Ubuntu 10.04* as well as *64-bit Ubuntu 12.04*. If you are not using exactly these versions, it won't work, likely, or you need to hack a lot --- or you need to translate your own version from source --- or you need to wait until your distribution adds a package.
A bientôt,
Armin.
participants (7)
-
Alex Gaynor -
Amaury Forgeot d'Arc -
Armin Rigo -
Felipe Cruz -
Maciej Fijalkowski -
Phyo Arkar -
wlavrijsen＠lbl.gov