I don't think there is plenty of time. With the current release cycle, python 2 will be unmaintained before the next major release. The implications could even be that python 2 will no longer be available in the package manager because security/platform fixes are no longer delivered. I highly recommend switching to Python 3 with the KiCad 5.1 release to prevent future issues, as well as to make the switch sooner than later. People will have to port their scripts anyway at some point.
I assume we cannot use Python2+3 inside the GUI concurrent due to symbol issues (like with GTK2+GTK3), but at least when used as CLI script support for both versions should be possible.
It seems wxPython is available for Windows as well: https:/ /pypi.org/ project/ wxPython/ #files
There is some discussion going on about that in the forum: https:/ /forum. kicad.info/ t/moving- from-python- to-lisp- lua/11691/ 48
I don't think there is plenty of time. With the current release cycle, python 2 will be unmaintained before the next major release. The implications could even be that python 2 will no longer be available in the package manager because security/platform fixes are no longer delivered. I highly recommend switching to Python 3 with the KiCad 5.1 release to prevent future issues, as well as to make the switch sooner than later. People will have to port their scripts anyway at some point.
I assume we cannot use Python2+3 inside the GUI concurrent due to symbol issues (like with GTK2+GTK3), but at least when used as CLI script support for both versions should be possible.