> On 1 Apr 2024, at 18:14, Left Right via Python-list
> wrote:
>
> It sounds weird that symbols from Limited API are _missing_ (I'd
> expect them to be there no matter what library version you link with).
You have to specify the version of the limited API that you want to use.
Each release ad
It sounds weird that symbols from Limited API are _missing_ (I'd
expect them to be there no matter what library version you link with).
But, I haven't done this myself, so, what do I know? It would help
though to see the actual error.
That aside: why do you want to do this? One side effect of doi
> 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
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 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
I have a python module that includes some C++ code that links with the
Python C API
I have now modified the c++ code so that it only uses the Limited API,
and linked with python3.lib instead of python311.lib.
I can now use that python module with different python versions on Windows
But on Linux
