Is there really anything unexpected here? I would have thought that it is obvious that when importing some library, that library will execute code already at im

Is there really anything unexpected here? I would have thought that it is obvious that when importing some library, that library will execute code already at import time. And that you can do strange things, esp when messing with the underlying C structures, should also be clear. Even in C itself, you can do the same in shared libraries. It's a very important functionality that the library can run some init code when it is being loaded. And you can do all kinds of strange things, modifying some random memory.