On 10/03/23 10:59 am, Cameron Simpson wrote: > I think this might be the common case of a module which wraps another > library It's not quite the same thing, though -- the library it wraps is already hooked into things behind the scenes in ways that may not be obvious. (Unless you're Dutch?) -- Greg