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 doing what you want will be the "weird" name of your wheel archive. Weird in a sense that virtually nobody does that. And when virtually nobody does something, you are almost guaranteed to be the first to find bugs, and then be the one whose bug reports are shoved into the backlog and never looked at again. You, kind of, are already walking into the world of pain trying to make Python binary packages, and then you also want them to be cross-platform, and then you want them to be usable by different versions of Python... Unless it's for your own amusement, I'd just have a package per version of Python. Maintenance-wise it's going to be a lot easier. On Fri, Mar 29, 2024 at 10:13 AM Barry via Python-list <python-list@python.org> wrote: > > > > > On 28 Mar 2024, at 16:13, Olivier B. via Python-list > > <python-list@python.org> 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 Windows? > > Python limited API works on linux, but you do not link against the .so on > linux I recall. > > You will have missed that libpython3.so is a symlink to libpython3.11.so.10. > > Windows build practices do not translate one-to-one to linux, or macOS. > > Barry > > > -- > https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
