I think ‘wt+’ is a programming error. I recall that the original developer was initially having some difficulty getting the pipes to open correctly on Linux.
This works for me with Python 2.7 and Python 3.4:
tofile = open( toname, 'w' )
Note also that at line 54, the line is indented with a tab character - strictly speaking, that should be replaced with spaces.
When I run pipe client on my windows 10 machine I get the error
FileNotFoundError: [Errno 2] No such file or directory: '\\\\.\\pipe\\ToSrvPipe'
This comes from line 160.
self._write_pipe = open(WRITE_NAME, 'w')
When I run pipe test I get the following output:
pipe-test.py, running on windows
Write to "\\.\pipe\ToSrvPipe"
Read from "\\.\pipe\FromSrvPipe"
-- Both pipes exist. Good.
Traceback (most recent call last):
File "./pipe.py", line 44, in <module>
TOFILE = open(TONAME, 'w')
FileNotFoundError: [Errno 2] No such file or directory: '\\\\.\\pipe\\ToSrvPipe'
The only way I can get that error is by disabling the module. Are you absolutely sure that mod-script-pipe is still enabled (AND you restarted Audacity after enabling it)?
I’ve discovered some peculiarities in the behaviour of mod-script-pipe in recent versions of Audacity, but I’m not able to progress further diagnosing the problem that you describe Gibbz without further information about what you are using and what you are doing.
I am using audacity version 2.3.2 python 3.7
I have tried disabling the mod-pipe, restart, enable, restart, then run the script.
Tried executing the script from the desktop, and also the audacity folder (C:\Program Files (x86)\Audacity).
No other version. Ive just grabbed the new audacity, installed over the old, and thought to enable it to see if its useful for something I want to do.
Would an uninstall - reinstall be likley to fix the issue? Or are there some config files around in my user directory?