Comment 6 for bug 1853496

Ian was not suggesting this is related to Windows, but to 'Windows packaging', i.e. the act of pulling together all the files (including anything python related) to create the installer. The fact that things work right when you go back to previous KiCAD releases proves that something incorrect was made with 5.1.5

Can anyone at least confirm my finding on the shipped python version? From a Windows command prompt:
"C:\Program Files\KiCad\bin\python.exe" --version

The issue with EEschema can be easily worked around by pointing to an external python installation.
However I am struggling to workaround the same issue to use the pcbnew python module standalone - I can get as far as:

    import pcbnew
  File "C:\Program Files\KiCad\lib\python2.7\site-packages\pcbnew.py", line 15, in <module>
    import _pcbnew
ImportError: DLL load failed: The specified module could not be found.

Even though I have appended to the python path every single path I could query from PCBNew embedded python shell:

sys.path.append('C:\\Program Files\\KiCad\\lib\\python27.zip')
sys.path.append('C:\\Program Files\\KiCad\\lib\\python2.7')
sys.path.append('C:\\Program Files\\KiCad\\lib\\python2.7\\plat-win32')
sys.path.append('C:\\Program Files\\KiCad\\lib\\python2.7\\lib-tk')
sys.path.append('C:\\Program Files\\KiCad\\lib\\python2.7\\lib-old')
sys.path.append('C:\\Program Files\\KiCad\\lib\\python2.7\\lib-dynload')
sys.path.append('C:\\Program Files\\KiCad\\lib\\python2.7\\site-packages')
sys.path.append('C:\\Program Files\\KiCad\\lib\\python2.7\\site-packages\\wx-3.0-msw')
sys.path.append('C:\\Program Files\\KiCad\\share\\kicad\\scripting')
sys.path.append('C:\\Program Files\\KiCad\\share\\kicad\\scripting\\plugins')
sys.path.append('C:\\Program Files\\KiCad\\bin')
sys.path.append('C:\\Program Files\\KiCad\\bin\\plugins\\3d')

I have a sign-off flow which performs a number of steps, some of which requires the pcbnew python module, so moving completely inside pcbnew is not an option for me.

Can the windows builder be cross checked?
Also, seeing that the whole depot is migrating to gitlab, should this issue be re-opened there?

Thanks,
nico