no windows support

[krunch3r76]

the named pipe feature is not supported by Python in windows; however, it appears to be supported in powershell (reference needed). this is being researched along with alternative IPC tools.

references:
https://hackinparis.com/data/slides/2017/2017_Cohen_Gil_The_forgotten_interface_Windows_named_pipes.pdf
https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-callnamedpipea
https://rkeithhill.wordpress.com/2014/11/01/windows-powershell-and-named-pipes/

[krunch3r76]

while named pipes are well supported in dot net including via powershell, python does not provide standard library support on windows. therefore, windows support will need to implement an IPC mechanism besides named pipes that is ideally supported by the standard library as expecting third party packages to be up to date with asynchronous mechanisms is probably too much to expect at this time. however, windows support is somewhat available via WSL in which case an alternative interface to the named pipe in the wsl environment may be sufficient.

[krunch3r76]

python docs hint of interoperability strategies with windows named pipes in the Listeners and Clients section at multiprocessing.connection 17.2

[krunch3r76]

python has ipc support using windows named pipes:
https://docs.python.org/3/library/multiprocessing.html#module-multiprocessing.connection