Sometimes libraries do a switcheroo where they run interpreted code on startup to locate the "real" implementation in a shared object, and then load that and re

Sometimes libraries do a switcheroo where they run interpreted code on startup to locate the "real" implementation in a shared object, and then load that and replace themselves with it. I'm not sure this is really idomatic, but here's an example of what it looks like from OpenCV: https://github.com/opencv/opencv/blob/master/modules/python/package/cv2/__init__.py https://github.com/opencv/opencv/blob/master/modules/python/...