Leysin Winter Sprint: reported
|
Update: the sprint has been reported to some later date. The next PyPy sprint will probably still be in Leysin, Switzerland, for the seventh time. |
|
The PyPy blogposts
Create a guest post via a PR to the source repo
Recent Posts
- Some Ways that PyPy uses Graphviz
- PyPy v7.3.4: release of python 2.7 and 3.7
- New HPy blog
- PyPy's blog has moved
- Mac meets Arm64
- PyPy 7.3.3 triple release: python 3.7, 3.6, and 2.7
- PyPy 7.3.2 triple release: python 2.7, 3.6, and 3.7
- PyPy is on Open Collective
- A new chapter for PyPy
- PyPy 7.3.1 released
Archives
Tags
- arm (1)
- cli (1)
- compiler (1)
- cpyext (3)
- CPython (3)
- ep2008 (1)
- extension modules (2)
- GraalPython (1)
- hpy (1)
- Heptapod (1)
- jit (18)
- jython (1)
- kcachegrind (1)
- numpy (24)
- parser (1)
- profiling (1)
- pypy (6)
- pypy3 (16)
- PyQt4 (1)
- release (49)
- releasecffi (3)
- releaserevdb (1)
- releasestm (1)
- revdb (1)
- roadmap (1)
- RPyC (1)
- speed (3)
- sprint (3)
- stm (14)
- sun (1)
- Smalltalk (1)
- Squeak (1)
- unicode (1)
- valgrind (1)
Comments
It would be nice if there are prebuilt binaries in the next release.
Certainly if it's faster there are a lot of graphics based projects where this would be interesting (pygame, pygelt, cocos2d, shoebot etc).
@Anonymous:
Probably they would be still slower, because ctypes is very slow in PyPy afaik.
Someone mentioned in irc that the long time goal for ctypes is, that the jit doesn't use libffi at all but does direct assembler-to-c calls instead, if I remember correctly. - what should be superfast.
That would of course be absolutely awesome. :)
(and it's also the secret reason, why I only use pypy compatible modules for my pyglet game ;)
Unfortunately I don't know if this is going to happen anytime "soon" / before the 1.2 release (at least I can't find it on extradoc/planning/jit.txt) but I know many people who would instantly drop cpython then. :P
Heck, if I only had more clue about, how difficult this is to implement...