Started using Limited API in order to eliminate need of module recompilation.

[KOLANICH]

No description provided.

[baskiton]

Thanks for the contribution!
However, this option doesn't make sense, since the extension is kernel-specific, depends on the kernel version, and the wheels are not loaded on PYPI. As a result, the extension is built on the end device.
For this option to be useful, wheels must be built for all manylinux* targets. If you know how to do this, I will be glad to accept the appropriate contribution.

[KOLANICH]

However, this option doesn't make sense, since the extension is kernel-specific, depends on the kernel version

Do you mean it has to be recompiled on every kernel upgrade? The main motivation was just to compile it for Python 3.11 installed on my machine and then to reuse on all the next versions of Python without any burden of recompiling by just moving the dirs of the installed package into new loacations (I do it after the distro changes Python version). The wheel somehow contains Python version within metadata and wheel name IDK why, but the library compiled looks like version invariant and I guess that when moved to Pythonn 3.12 dir it should work.

For this option to be useful, wheels must be built for all manylinux* targets. If you know how to do this

I have never done it personally, but AFAIK there are special Docker images https://github.com/pypa/manylinux (which are Docker images with old libc) and a special tool https://github.com/pypa/auditwheel converting wheels built there into "manylinux wheels" by fixing their metadata and bundling shared libs. But this package depends on no other external shared libs other than Python API and libc.

[baskiton]

Do you mean it has to be recompiled on every kernel upgrade?

No. We are talking about cardinal changes in the kernel when new features appear. For example, for this package, according to man setns, the main kernel milestones are:

• Linux 3.0 (minimal version)
• Linux 3.8
• Linux 4.6
• Linux 5.8

by just moving the dirs of the installed package into new loacations

Ah, that sounds logical. It turns out that I did not quite understand the purpose of this option. Thought you wanted the wheels to be built by the builder and stored in PYPI to save the end user the burden of compiling.
Ok, I'm restoring the PR.