The recent announcement by Guido van Rossum
that he was stepping away from
his “benevolent dictator for life” (BDFL) role for Python was met with some
surprise, but not much shock, at least in the core-developer community.
Van Rossum has been telegraphing some kind of change, at some unspecified
point, for several years now, though the proximate cause (the “PEP 572 mess“) is
unfortunate. In the meantime, though, the project needs to figure out
how to govern itself moving forward—Van Rossum did not appoint a successor
and has left the governance question up to the core developers.
system tends to be overloaded in its own way. If one’s goal is to
maximize the use of the available computing resources, overutilization
tends not to be too far away, but when it happens, it can be hard to tell
where the problem is. Sometimes, even the fact that there is a problem at
all is not immediately apparent. The
pressure-stall information patch set from Johannes Weiner may make life
easier for system
administrators by exposing more information about the real utilization
state of the system.
in the wake of the difficult PEP 572 discussion, to step down from his
leadership of the project. “Now that PEP 572 is done, I don’t ever want to have to fight so hard for a
PEP and find that so many people despise my decisions.
I would like to remove myself entirely from the decision process. I’ll
still be there for a while as an ordinary core dev, and I’ll still be
available to mentor people — possibly more available. But I’m basically
giving myself a permanent vacation from being BDFL, and you all will be on
variety of filesystem types, and each has its own,
often extensive set of options. As a result, the mount()
system call is complex, and the list of mount
options is a rather long read. But even with all of that complexity,
mount() does not do everything that users would like. For
example, the options for a mount operation must all fit within a single
4096-byte page — the fact that this is a problem for some users is
illustrative in its own right. The
problems with mount() have come up at various meetings, including
at the 2018 Linux Storage, Filesystem, and
Memory-Management Summit. A set
of patches implementing a new approach is getting closer to being
ready, but it features some complexity of its own and there are some
remaining concerns about the proposed system-call API.
The LWN.net Weekly Edition for July 12, 2018 is available.