On Thu, Jun 02, 2022 at 09:15:40PM +0200, Alec Leamas wrote: > > > I try handle a package which installs a partly compiled, > > > architecture-dependent python module. Until now this has been done in > > > /usr/lib/triplet/python3.10/site-packages. This scheme has basically > > > worked > > > fine. > > > > > > However, here is an Ubuntu bug [1] where a user runs into problems because > > > this installation path is not in sys.path by default. > > > > > > I have been trying to look in the python policy docs, but cannot find the > > > exact way to install code like this, in the policy [2] > > > parlance an "extension module". > > Not sure where is this documented but you can easily check on your system. > > It should be /usr/lib/python3/dist-packages/*.cpython-3*-x86_64-linux-gnu.so > > > Hm...this is not what I have. Did I get get the term "Extension module" > wrong? Well, we don't know what do you have. Extension modules are ones you import.
> That aside, what I have is some python3 scripts and a compiled .so library > invoked form the python code. The whole thing designed to be in the same > directory. And the question is how this should be installed... Invoked how? -- WBR, wRAR
signature.asc
Description: PGP signature
