I have been using plugins created by Jean-Samuel Reynaud, which worked great. I just have problems with the viastitching plugin. So here are the errors.
I created a very simple layout with two pin headers with nets /sig and /gnd, and two metal filled areas all connected to net /gnd.
Then opened the viastitching tool (without preselecting any drawings). I left everything default and selected the net as /gnd.
Then after I click run, I got the following errors.
“Program Files” in your pathname suggests Windoze, but I also see both slashes and back slashes.
I also see reference to Python 2.7 while KiCad is trying to move on to Python V3.
On top of that, why bother for a script for via’s at all?
I assume it’s an old script, probably for KiCad V4 and in KiCad V5 you can just drop via’s on a zone or on tracks and they become part of the net that they are connected to. There is not much need to use a script for via’s anymore.
Taking offense to some silly words without any regard to context seems to be the fashion these days. Just as using “master” and “slave”, and treating those words just as if the SPI interface of my uC could be insulted.
With both slashes and backslashes in a pathname the path is not valid regardless of what operating system you use.
Good you verified that. I’m not deep into KiCad development, but apparently KiCad depends on some old libraries which have (had?) not been ported to Python V3 yet on some OS’es. I think (but am not sure) that Python V2 has been completely dropped from KiCad on Linux.
Unfortunately, that is true on Windows (Windoze, Winblows, M$Win, etc… As a Win10 user I use whichever of those derogatory variants as fits my current mood). There are some support libraries that the Windows compiler environment depends on that are still stuck on Python2.7 so as a result KiCad on Win is also stuck on Python2.7. I think there is some progress to fix this, but the effort isn’t our KiCad developers alone. Even if our devs submit fixes to those other development teams, it is up to the other development teams to implement the fixes. Such is the cost of not reinventing every wheel.