Since I've been poking around in this area of CPython lately, here's some triviaassociated with frame objects.

First, one might wonder if code executing at the module level literallyhas a CPython frame struct with f_locals being the same as f_globals , or if the C code just leaves f_locals null and fixesthings up behind the scenes when you look from Python code. Theanswer turns out to be that CPython frame structures always havea real f_locals (Python) dictionary

As I noted in passing , Python frame objects alsohave a vaguely mysterious f_builtins member. On one level, frameobjects have this member because they are more or less representationsof the CPython (code) frame structure, and the C-level code framestructure has an f_builtins field. So, what is this field?

(Quite a lot of the Python internal objects work this way; they have themembers that they do mostly because they're Python representations of Cstructures).

We can

I've written before about Ubuntu'ssubstandard kernel update management; what I didn't say then (partlybecause I didn't fully understand it) is that this is just amanifestation of a general problem with kernel packaging in Ubuntu (andDebian, which it inherits from).

The fundamental problem for packaging kernels on Debian and Ubuntu isthat there are two unfortunate design choices in dpkg , the Debianpackage system: you can only every have one version of a packageinstalled at once, and there