One of my serious irritations with ZFS is how various ZFS commands (orat least sub-commands of zpool ) will stall badly if it can't talk tosome of the underlying disk devices. This is especially apparent whenyou're using iSCSI; for example, I accidentally booted a system with theiSCSI cable plugged into the wrong port, and once the system had booted zpool list simply hung.

(Worse, it hung uninterruptibly; I could not stop it with ^C, use jobcontrol to background

One of the things that would be useful in an access tracer is reporting not just what was accessed, butwhere it was accessed from. A basic starter for this is knowing whatfunction called you.

CPython has enough introspection faculties to give youthis information, but it's not entirely documented how todig it out. The big tool for this is the inspect module , and wecan use it to define a function:

import inspect

def getcallerinfo():    fr = inspect.currentframe()    try:         fr

Here's a question: which type of documentation is the ever-popular FAQ format?

My answer is that in practice, FAQs are a collection of tutorials; theytell you how to do various specific frequently asked operations. Thishas important implications if your primary documentation format is FAQs,because FAQs effectively have drawbacks from both sides; they're notas well organized or as comprehensive as reference documents, and theydon't give you an overall view the way a single unified tutorial does.

(That they