I did use the full python3.10 in the shebang. I have both 3.9 and 3.10 installed. All works just fine with either python3 (which is 3.9 as it is in /usr/local/bin and comes up before /usr/local/opt/python(a)3.10/bin) and it works fine with python3.9, in the #! line, but not 3.10. It is possible there is some odd interaction between 3.9 and 3.10, but as I have it working with 3.9 and need it for the next week, I'm not in a position to completely remove 3.9 at this stage. I did also try with a modified path so that the /usr/local/opt/python(a)3.10/bin was before /usr/local/bin, but that made no difference. Александар Средојевић <ferrumite666(a)gmail.com> writes: > On Mon, 01 Aug 2022 08:49:18 +1000 Tim Cross wrote: >> For me, almost immediately. >> >> If I run ./mac at a command prompt, I hear the little bit of intro >> speech and the server sits their, looking like it is waiting for >> input. However, as soon as I hit any key, the server immediately exits. >> >> If I run Emacs, I here the initial spoken feedback, but then get no >> speech. There are no errors or warnings or anything saying something >> like "Process speaker not running" as you would normally see with other >> speech servers. Everything appears to work, but there is no speech >> output. > I actually had a similar issue while the shebang line was running > python2, and it seemed to get fixed when I pointed it two python3 as > described earlier in the thread. What is your first line of the > servers/mac script? >> Note that with the homebrew 3.10 install, on my system, all the >> 'binaries' are put into /usr/local/opt/python(a)3.10/bin and none are >> linked into /usr/local/bin due to potential conflict with the homebrew >> python3. To resolve this, I added the pythong3.10 bin path to the start >> of my PATH variable. > Can you try running the server with the full path to python3.10? Like > this: > > $ /usr/local/Cellar/python(a)3.10/3.10.5/bin/python3 mac
|May 1995 - Last Year|Current Year|
If you have questions about this archive or had problems using it, please contact us.