Connection by the user of GPL modules in closed software: who violates?

Question

Copyright

I am writing a software that I definitely plan to release under the EULA.
I write in Python and plan to implement a highly modular system with dynamic imports. The problem is that modules can be under the GPL and it is not clear who is then responsible for violating the GPL conditions and whether this is a violation at all, because the user himself specifies which module to connect to (in the config, for example).
Who understands, can you tell?

Answer 1

Below is a piece describing how this problem is solved in SUSE, in relation to modules that are not entirely clean from the point of view of the license.
Each of these conditions is represented by a particular flag in the kernel. Some Linux vendors, such as SUSE, add additional taint flags to indicate conditions such as loading a module that is not supported by the vendor.