We should also be thinking of when we want to officially drop the Python 2 support for KiCad. Since Python 2.7 will be end of life in just a few months, it might be worth starting the transition over to Python 3 (it looks like Windows and Mac builds ship with 2.7 currently).
-Ian On Sat, Oct 26, 2019 at 3:52 PM Carsten Schoenert <c.schoen...@t-online.de> wrote: > Hello Wayne, > > Am 26.10.19 um 15:53 schrieb Wayne Stambaugh: > > I'm guessing that fixing the shebangs will not be enough because there > > is python2 specific code in the script files. > > I think so, I've haven't looked at the Python3 compatibility of the > underlying code, just grep'd for potential shebang lines. Looking at the > date within the copyright statement let me be quite sure the files wont > be Python3 ready. > > And this is for sure true for mostly all the existing files. > > -- > Regards > Carsten Schoenert > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp