> On 28 Mar 2024, at 16:13, Olivier B. via Python-list
> wrote:
>
> But on Linux, it seems that linking to libpython3.so instead of
> libpython3.11.so.1.0 does not have the same effect, and results in
> many unresolved python symbols at link time
>
> Is this functionality only available on W
It is not a symlink on my system, where i built python myself, but a
15KB so file. But it seems to lack lots of python symbols.
Maybe what i should do is actually make libpython.so a physical copy
of libpyton311.so before linking to it, so now on any system the
module would look to load libpython.
> On 29 Mar 2024, at 16:09, Olivier B.
> wrote:
>
> It is not a symlink on my system, where i built python myself, but a
> 15KB so file. But it seems to lack lots of python symbols.
>
> Maybe what i should do is actually make libpython.so a physical copy
> of libpyton311.so before linking to
