Re: [BRLTTY] Support multiple Python versions on Windows
Hi Samuel, Thanks a lot for looking. Would it be possible to provide a test build of the python bindings based on this pr? Cheers, Leonard On 08/10/2023 21:26, Samuel Thibault wrote: Hello, Samuel Thibault, le jeu. 28 sept. 2023 01:28:01 +0200, a ecrit: Samuel Thibault, le jeu. 28 sept. 2023 01:26:57 +0200, a ecrit: Apparently cython3 introduced some support for it, so it will be worth trying it indeed. (namely: CYTHON_LIMITED_API, that makes cython use the stable ABI) I tried it, it seems to be working indeed. I have submitted the change on https://github.com/brltty/brltty/pull/429 Samuel ___ 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
Re: [BRLTTY] Generic udev rules even with manufacturer filters?
[quoted lines by Samuel Thibault on 2023/10/08 at 21:43 +0200] >In the generated usb-generic.rules file, we can read > >ENV{PRODUCT}=="403/6001/*", ATTR{manufacturer}=="Hedo Reha Technik GmbH", >ENV{BRLTTY_BRAILLE_DRIVER}="hd", GOTO="brltty_usb_run" >ENV{PRODUCT}=="403/6001/*", ATTR{manufacturer}=="Tivomatic Oy", >ENV{BRLTTY_BRAILLE_DRIVER}="at", GOTO="brltty_usb_run" > >Shouldn't these be put in usb-customized.rules? AIUI the manufacturer >filtering should avoid any conflict with other FTDI-using devices? In theory, yes. The "problem" is that the generating script doesn't (yet) know which manufacturer names aren't generic. In other words, some generic chips have their generic manufacturer names configured. I rather doubt that the chip manufacturers do that but do suspect that some braille device manufacturers do. -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: d...@mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 | ___ 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
[BRLTTY] Generic udev rules even with manufacturer filters?
Hello, In the generated usb-generic.rules file, we can read ENV{PRODUCT}=="403/6001/*", ATTR{manufacturer}=="Hedo Reha Technik GmbH", ENV{BRLTTY_BRAILLE_DRIVER}="hd", GOTO="brltty_usb_run" ENV{PRODUCT}=="403/6001/*", ATTR{manufacturer}=="Tivomatic Oy", ENV{BRLTTY_BRAILLE_DRIVER}="at", GOTO="brltty_usb_run" Shouldn't these be put in usb-customized.rules? AIUI the manufacturer filtering should avoid any conflict with other FTDI-using devices? Samuel ___ 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
Re: [BRLTTY] Support multiple Python versions on Windows
Hello, Samuel Thibault, le jeu. 28 sept. 2023 01:28:01 +0200, a ecrit: > Samuel Thibault, le jeu. 28 sept. 2023 01:26:57 +0200, a ecrit: > > Apparently cython3 introduced some support for it, so it will be worth > > trying it indeed. > > (namely: CYTHON_LIMITED_API, that makes cython use the stable ABI) I tried it, it seems to be working indeed. I have submitted the change on https://github.com/brltty/brltty/pull/429 Samuel ___ 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