Thanks Peter for the details!
Yes, of course fzp_checker_runner uses python3
I am a bit surprised to read about python2 in cygwin. It was replaced by python3 since 2008, and finally sunset in 2020, see also Sunsetting Python 2 | Python.org .
About the error message you encountered, I think it is significant. The script currently expects a file structure like in fritzing-parts (for parts included in Fritzing).
Standalone parts, like fzpz, or extracted fzpz files, are not yet taken into account.
Yes I discovered that and when I converted the part to repository format it works fine. When I get some time I’ll look it over and see if I can get my head around what it does and add anything that I think is useful from FritzingCheckPart.py and add the .fzpz code. I may make a pull request to reformat some of the long lines (I have been using pycodestyle to check my python to see it meets coding standards ) and it complains a bit. I expect it is going to take me some time to get to it though, after I either fix pythonpartsfactory or give up I expect. My cygwin is old and may still be supporting python 2 (although I would have thought they would have deleted it and I have updated recently) Ah! Yes I have old pythons 2.7 which are marked as Orphaned. I guess they haven’t been deleted as they are marked keep I’ll have to figure out how to delete them so as to not cause problems in future.
I looked into fzpz support, and have a first working draft just right now.
Basically the fzpz needs to be unzipped to tmp, and most parts of the script use a get_svg_path method, that can be adapted to support the flat directory structure.
I’ll run some more checks and a review, and probably can update the script on github until next week.
