kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

>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 they seemed to think that that was our problem
even though they broke the previous wxPython build behavior.  I haven't
tried it in a while but I have been following the project on github and
I have not seen any commits that addressed this issue.  Given the
response I got last time, my motivation is low to fix the issue myself.
 None the less, there is currently no wxPhoenix/Python3 support for windows.

On 10/26/19 12:41 PM, Nick Østergaard wrote:
> 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 <Ian.S.McInerney@xxxxxxxx
> <mailto:Ian.S.McInerney@xxxxxxxx>>:
> 
>     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.schoenert@xxxxxxxxxxx <mailto:c.schoenert@xxxxxxxxxxx>> 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@xxxxxxxxxxxxxxxxxxx
>         <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>         Unsubscribe : https://launchpad.net/~kicad-developers
>         More help   : https://help.launchpad.net/ListHelp
> 
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~kicad-developers
>     More help   : https://help.launchpad.net/ListHelp
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>