Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Steven A. Falco
On 10/26/19 10:46 AM, Carsten Schoenert wrote: > Am 26.10.19 um 16:09 schrieb Seth Hillbrand: >> I've added [1] so that we make sure to get to it before v6 is released. >> What is the timeline for the new stable Debian/Fedora?  Do we need to >> accelerate this for 5.1.6? > > The next Debian

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Seth Hillbrand
On 2019-10-26 10:06, Simon Richter wrote: Hi Wayne, On 26.10.19 19:00, Wayne Stambaugh wrote: None the less, there is currently no wxPhoenix/Python3 support for windows. TBH, I wouldn't like to be dependent on MSVC on Windows -- the compiler is great as an additional source of diagnostics,

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Wayne Stambaugh
Hi Simon, On 10/26/19 1:06 PM, Simon Richter wrote: > Hi Wayne, > > On 26.10.19 19:00, Wayne Stambaugh wrote: > >> None the less, there is currently no wxPhoenix/Python3 support for windows. > > TBH, I wouldn't like to be dependent on MSVC on Windows -- the compiler > is great as an

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Simon Richter
Hi Wayne, On 26.10.19 19:00, Wayne Stambaugh wrote: > None the less, there is currently no wxPhoenix/Python3 support for windows. TBH, I wouldn't like to be dependent on MSVC on Windows -- the compiler is great as an additional source of diagnostics, and some people might like the smaller

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Wayne Stambaugh
From what I can tell, this is going to be an issue. The wxPhoenix folks don't seem too keen on supporting mingw builds any more. The new wxPhoenix build scripts forcibly change the build environment to msvc even if you tell python distutils to use mingw. The last time I contacted the project

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Nick Østergaard
For windows, someone newds to show phoenix working in either msys2 or msvc. And if we will eventuallty transition to msvc we also need other dependencies easily available. I am still hoping for those dependencies to become available in vcpkg. lør. 26. okt. 2019 17.13 skrev Ian McInerney : > We

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Adam Wolf
The Mac Kicad Python 3 transition needed upstream work maybe a year ago. I have revisiting it on my list. Adam On Sat, Oct 26, 2019, 10:13 AM Ian McInerney wrote: > 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

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Ian McInerney
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,

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Carsten Schoenert
Am 26.10.19 um 16:09 schrieb Seth Hillbrand: I've added [1] so that we make sure to get to it before v6 is released. What is the timeline for the new stable Debian/Fedora? Do we need to accelerate this for 5.1.6? The next Debian stable release is planned for autumn 2021. So no rush needed.

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Seth Hillbrand
On 2019-10-26 06:53, Wayne Stambaugh wrote: I'm guessing that fixing the shebangs will not be enough because there is python2 specific code in the script files. I've added [1] so that we make sure to get to it before v6 is released. What is the timeline for the new stable Debian/Fedora? Do

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Carsten Schoenert
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

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Wayne Stambaugh
I'm guessing that fixing the shebangs will not be enough because there is python2 specific code in the script files. On 10/26/19 9:42 AM, Steven A. Falco wrote: > This will become an issue for Fedora as well. The command "python" used to > mean "python2", but as of Fedora 31 (due to be released

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-26 Thread Steven A. Falco
This will become an issue for Fedora as well. The command "python" used to mean "python2", but as of Fedora 31 (due to be released this Tuesday, 2019-10-29) the command "python" will mean "python3". Steve On 10/25/19 4:35 PM, Carsten Schoenert wrote: > Hi, > > as probably known

[Kicad-developers] Python files still depending on Python2 only due used shebang

2019-10-25 Thread Carsten Schoenert
Hi, as probably known Debian is planning to get Python2 removed within the next planned stable release. This requires no hard dependencies on Python2 of course in all related packages. The master branch (and of course also the branch 5.1) has still some Python scripts which do have a shebang