Düsseldorf Sprint Started
The Düsseldorf sprint starts today. Only Samuele and me are there so far, but that should change over the course of the day. We will mostly work on the JIT during this sprint, trying to make it a lot more practical. For that we need to decrease its memory requirements some more and to make it use less aggressive inlining. We will post more as the sprint progresses.
The PyPy blogposts
Create a guest post via a PR to the source repo
Recent Posts
- Guest Post: How PortaOne uses PyPy for high-performance processing, connecting over 1B of phone calls every month
- PyPy v7.3.17 release
- Conda-forge proposes sunsetting support for PyPy
- A Knownbits Abstract Domain for the Toy Optimizer, Correctly
- Abstract interpretation in the Toy Optimizer
- Mining JIT traces for missing optimizations with Z3
- Finding Simple Rewrite Rules for the JIT with Z3
- Profiling PyPy using the Firefox profiler user interface
- PyPy v7.3.16 release
- Fixing a Bug in PyPy's Incremental GC
Archives
Tags
- arm (2)
- casestudy (3)
- cli (1)
- compiler (1)
- conda-forge (1)
- cpyext (4)
- CPython (3)
- ep2008 (1)
- extension modules (3)
- gc (1)
- guestpost (1)
- GraalPython (1)
- hpy (1)
- Heptapod (1)
- jit (22)
- jython (1)
- kcachegrind (1)
- meta (1)
- numpy (24)
- parser (1)
- performance (2)
- profiling (4)
- pypy (6)
- pypy3 (16)
- PyQt4 (1)
- release (62)
- releasecffi (3)
- releaserevdb (1)
- releasestm (1)
- revdb (1)
- roadmap (2)
- RPyC (1)
- speed (6)
- sponsors (7)
- sprint (3)
- sprints (1)
- stm (14)
- sun (1)
- Smalltalk (1)
- Squeak (1)
- testing (1)
- toy-optimizer (4)
- unicode (1)
- valgrind (1)
- z3 (3)
Comments
Looking forward to amazing new developments...
Are you planning a new release anytime soon? (hopefully with JIT?)
A release is planned for the February-March timeframe.
/Jacob Hallén
Actually, I would plan the release for the end of the next sprint, which should be in January.