LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Monday, August 2nd, 2021
| Time |
Event |
| 1:49p |
Kernel prepatch 5.14-rc4 The 5.14-rc4 kernel prepatch is out for testing. " Nothing to see here, entirely normal rc4". | | 2:47p |
Security updates for Monday
Security updates have been issued by Arch Linux (389-ds-base, consul, containerd, geckodriver, powerdns, vivaldi, webkit2gtk, and wpewebkit), Debian (aspell, condor, libsndfile, linuxptp, and lrzip), and Fedora (bluez, buildah, java-1.8.0-openjdk, java-11-openjdk, java-latest-openjdk, kernel, kernel-tools, mbedtls, mingw-exiv2, mingw-python-pillow, mrxvt, python-pillow, python2-pillow, redis, and seamonkey). | | 2:56p |
Stable kernel updates Stable kernels 5.13.7, 5.10.55, 5.4.137, and 4.19.200 have been released. As usual, there are important fixes and users should upgrade. | | 3:37p |
GNU C Library 2.34 released
Version 2.34 of the GNU C library has been released. Significant changes
include the folding of libpthread, libdl, libutil, and libanl into the main
library, support for 64-bit (year-2038 safe) times on 32-bit systems,
support for the close_range() system call, a handful of security
fixes, and many other changes. | | 5:15p |
[$] Kernel topics on the radar
The kernel-development community is a busy place, with thousands of emails
flying by every day and many different projects under development at any
given time. Much of
that work ends up inspiring articles at LWN, but there is no way to ever
cover all of it, or even all of the most interesting parts. What follows
is a first attempt at what may become a semi-regular LWN feature: a quick look
at some of the work that your editor is tracking that may or may not show
up as the topic of a full article in the future. The first set of topics
includes memory folios, task isolation, and a lightweight threading
framework from Google. | | 9:44p |
Watson: Launchpad now runs on Python 3 On his blog, Colin Watson has a lengthy reflection on moving the code for Ubuntu's Launchpad software-collaboration web application from Python 2 to Python 3. He looks at some of the problem areas for upgrading, both in general and for Launchpad specifically, some pain points that were encountered, lessons learned, and the nine known regressions that reached the Launchpad production code during the process.
I’m not going to defend the Python 3 migration process; it was pretty rough in a lot of ways. Nor am I going to spend much effort relitigating it here, as it's already been done to death elsewhere, and as I understand it the core Python developers have got the message loud and clear by now. At a bare minimum, a lot of valuable time was lost early in Python 3's lifetime hanging on to flag-day-type porting strategies that were impractical for large projects, when it should have been providing for "bilingual" strategies (code that runs in both Python 2 and 3 for a transitional period) which is where most libraries and most large migrations ended up in practice. For instance, the early advice to library maintainers to maintain two parallel versions or perhaps translate dynamically with 2to3 was entirely impractical in most non-trivial cases and wasn't what most people ended up doing, and yet the idea that 2to3 is all you need still floats around Stack Overflow and the like as a result. (These days, I would probably point people towards something more like Eevee's porting FAQ as somewhere to start.)
|
|