location of arch-dependent python module
I am trying to package a program which contains a Python module. This
module is not written in Python, but in C++/pybind11. It seems to me
that the '.so' file this produces should go into an arch-dependent
However, these are not part of 'site.path' on Debian, and so they will
not be picked up with an 'import ...'.
Am I misinterpreting the rules? Or do you expect users to set
'site.path' for such packages themselves?