Hi Dave,
Thanks for the quick response.
May be I should setup a dev environment myself first to experiment a
bit, but I'm slightly puzzled about the docs. What should I do if I want
to create a x86 python module? Should I go with Cygwin or min-GW, and
should it be explicitly X86 or can X64 builds of either cygwin or MinGW
perfectly create X86 modules?
Cheers,
Leonard
On 27-9-2023 22:38, Dave Mielke wrote:
[quoted lines by Leonard de Ruijter on 2023/09/27 at 19:51 +0200]
The NVDA project is currently in the process of upgrading Python to version
3.11. I recall that when we updated to Python 3.7 3 years ago, I had to
create a brlapi python extension manually, as the python version bundled in
the Windows packages didn't match Python 3.7.
Python has something like the stable application binary Interface (ABI), see
https://docs.python.org/3.11/c-api/stable.html . This can be used by enabling
the limited API.
I wonder, has this ever been considered? If not, could it be considered to
create a brlapi python package that uses the limited API, preferably using an
API version that is equal to the minimum Python version that is still in
maintenance (currently 3.8)? That would ensure that you'd be able to use a
brlapi python extension with multiple python versions.
I'm the one who does the builds for Windows but I'm not a Windows person. If
you can give me the steps to perform to try to get it right, that'd be cool!
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty
