Tags¶
cli¶
cpyext¶
cpython¶
gc¶
hpy¶
jit¶
profiling¶
- (Cape of) Good Hope for PyPy
- How to make your code 80 times faster
- Inside cpyext: Why emulating CPython C API is so Hard
pyodide¶
pypy¶
- (Cape of) Good Hope for PyPy
- A snake which bites its tail: PyPy JITting itself
- Binary wheels for PyPy
- EuroPython 2010 Videos available
- EuroPython 2010 report
- First pypy-cli-jit benchmarks
- Gothenburg sprint report
- How to ignore the annoying Cython warnings in PyPy 6.0
- How to make your code 80 times faster
- Improve .NET Integration
- Improving Memory Behaviour to Make Self-Hosted PyPy Translations Practical
- Inside cpyext: Why emulating CPython C API is so Hard
- Next sprint: Vilnius/Post EuroPython, 10-12th of July
- Pdb++ and rlcompleter_ng
- PhD Thesis about PyPy's CLI JIT Backend
- Porting the JIT to CLI (part 1)
- Porting the JIT to CLI (part 2)
- Porting the JIT to CLI (part 3)
- Progresses on the CLI JIT backend front
- Py3k status update
- Py3k status update #2
- Py3k status update #3
- Py3k status update #4
- Py3k status update #5
- Py3k status update #6
- PyPy Genova-Pegli Post-EuroPython Sprint June 27 - July 2 2011
- PyPy code swarm
- PyPy for low-latency systems
- PyPy migrates to Mercurial
- PyPy v7.0.0: triple release of 2.7, 3.5 and 3.6-alpha
- PyPy wants you!
- PyPy.NET goes Windows Forms
- Realtime image processing in Python
- The peace of green
- Trying to get PyPy to run on Python 3.0
- Using Tkinter and IDLE with PyPy
- Using virtualenv with PyPy
pypy3¶
- Py3k status update
- Py3k status update #2
- Py3k status update #3
- Py3k status update #4
- Py3k status update #5
- Py3k status update #6
release¶
speed¶
- (Cape of) Good Hope for PyPy
- How to make your code 80 times faster
- Inside cpyext: Why emulating CPython C API is so Hard