Skip to main content

PyCon: Let's Talk About ????

David Beazley gave the keynote on the second day of PyCon. He decided to talk about PyPy.

PyPy made his code run 34x faster, without changing anything.

In theory, it's easier to add new features to Python using PyPy than cPython.

He's been tinkering with PyPy lately.

IPython Notebook is cool.

Is PyPy's implementation only for evil geniuses?

PyPy scares him because there is a lot of advanced computer science inside.

He doesn't know if you can mess around with PyPy.

It takes a few hours to build PyPy.

It needs more than 4G of RAM.

PyPy translates RPython to C. It generates 10.4 million lines of C code!

PyPy is implemented in RPython, which is a restricted subset of Python.

"RPython is [defined to be] everything that our translation toolchain can accept."

The PyPy docs are hard to read.

4513 .py files, 1.25 million non-blank lines of Python. convers RPython code to C.

The PyPy version is faster than the C version of Fibonacci! Although, if you turn on C optimizations, they're similar.

RPython is a restricted subset of Python that they used to implement the Python interpreter.

RPython can talk to C code. It's similar to ctypes.

RPython has static typing via type inference.

RPython has to think of the whole program and do type inferencing.

The implementation will blow your mind. It has "snakes and the souls of Ph.D students on the inside."

PyPy doesn't parse your Python. It uses Python code objects.

PyPy has a Python bytecode interpreter.

PyPy translates itself to C using its own bytecode interpreter.

They have regular Python and RPython in the same modules. They have the same syntax, but different semantics. Sometimes, they add docstrings with "NOT_RPYTHON" in them to keep track of which is which.

Stuff that happens at import time is normal Python. Code reached by the entry function is RPython.

They have a foreign function interface and something that's like autoconf.

They use decorators a lot.

"I still don't know how PyPy works."

"I don't even know how CPython works."

He does know how to use the things that make CPython work (ANSI C, Makefiles, etc.).

PyPy has a different set of tools: RPython,, metaprogramming, FFI.

Ruby is 3600x slower than Python on message-passing with a CPU-bound thread. They had a more extreme case of the same problem Python 3.3 had.

Ruby has a GIL.

He felt completely beat up and out of his league looking at the PyPy source. (I feel better now.)

Can you tinker with PyPy? He still doesn't know. He recommends that you do it anyway.


Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p