Attaching possible minimal fix for both issues. The hard-coded absolute paths which are checked should be removed, but that might affect other jessyInk modules as well, and should be done separately.
The error message returned from the spawned inkscape process on Windows 10 was:
'"inkscape --without-gui --version"' is not recognized as an internal or external command, operable program or batch file.
By passing the command as string instead of as list with a string as argument for Popen(), the external process is run successfully (tested with Inkscape 0.92.0 r15299 installed from 7z into custom location on Windows 10, and on OS X 10.7.5 with a regular linux-style command line installation into custom prefix).
On Windows, the export command then still fails (either hangs or takes a really long time) when rendering the layers of the SVG file to PNG or PDF at the specified resolution, but that is likely related to bug #1659172.
Attaching possible minimal fix for both issues. The hard-coded absolute paths which are checked should be removed, but that might affect other jessyInk modules as well, and should be done separately.
The error message returned from the spawned inkscape process on Windows 10 was:
'"inkscape --without-gui --version"' is not recognized as an internal or external command, operable program or batch file.
By passing the command as string instead of as list with a string as argument for Popen(), the external process is run successfully (tested with Inkscape 0.92.0 r15299 installed from 7z into custom location on Windows 10, and on OS X 10.7.5 with a regular linux-style command line installation into custom prefix).
On Windows, the export command then still fails (either hangs or takes a really long time) when rendering the layers of the SVG file to PNG or PDF at the specified resolution, but that is likely related to bug #1659172.