[Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Maciej Sumiński
Apparently mixing wxWidgets-gtk2 and wxPython-gtk3 [1] is not only an Arch issue anymore, as the upcoming Ubuntu release (bionic) also provides wxPython package built against gtk3 [package: 2, bug report: 3]. There are two things we can do to fix the problem for v5: - Backport python-wxgtk3.0 pack

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Jeff Young
I never got KICAD_SCRIPTING_WXPYTHON to work on my Mac, and I can’t say I’ve missed it. > On 10 Apr 2018, at 12:26, Maciej Sumiński wrote: > > Apparently mixing wxWidgets-gtk2 and wxPython-gtk3 [1] is not only an > Arch issue anymore, as the upcoming Ubuntu release (bionic) also > provides wxPy

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Maciej Sumiński
It seems the easy solution to me too. I just wonder how many people rely on the Python shell or GUIs done with wxPython. On 04/10/2018 01:32 PM, Jeff Young wrote: > I never got KICAD_SCRIPTING_WXPYTHON to work on my Mac, and I can’t say I’ve > missed it. > >> On 10 Apr 2018, at 12:26, Maciej Sum

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Nick Østergaard
FYI, it has been a problem on fedora for years. So it was not an issue on arch first. I guess there are multiple approaches to address this issue. 1. Platforms can disable the wxpython scripting option which will get rid of the footprint wizards and the python console. 2. Hack wxpython with gtk2 t

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Mitja Nemec
I'd hate to loose this feature primarily as an user of action plugins and as an author of them. On Tuesday, 10 April 2018, 13:36, Maciej Sumiński wrote: It seems the easy solution to me too. I just wonder how many people rely on the Python shell or GUIs done with wxPython. On 04/10/20

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Mitja Nemec
Miles Mccoo might have some new info regarding Phoenix (https://lists.launchpad.net/kicad-developers/msg31889.html) On Tuesday, 10 April 2018, 13:55, Nick Østergaard wrote: FYI, it has been a problem on fedora for years. So it was not an issue on arch first. I guess there are multiple

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread jp charras
Le 10/04/2018 à 13:54, Nick Østergaard a écrit : > FYI, it has been a problem on fedora for years. So it was not an issue on > arch first. > > I guess there are multiple approaches to address this issue. > 1. Platforms can disable the wxpython scripting option which will get rid of > the footpri

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Wayne Stambaugh
I wonder why they couldn't make a gtk2 version of wxPython. It seems plausible since they created a gtk2 version of wxWidgets. Looks like the work load just got increased during v6 development. Maybe we should attack that first and backport the gtk3 fixes to v5 so distros wont have to support gt

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Wayne Stambaugh
For our v5 release, I guess we are going to have to disable wxPython on the platforms who insist on building wxPython with gtk3. We can start looking at the transition to gtk3 and wxPhoenix during v6 development. Are distros actually shipping with wxWidgets built with gtk2 and wxPython built with

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Adam Wolf
Right now, one of the last blockers for the Mac v5 packaging efforts is wxpython. If it's having issues on other platforms, I may actually table that for a few days and see if we can get everything else going, and then we can have a good* (minus wxpython) rc2 for testing, and then tackle wxpython

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Wayne Stambaugh
I'm fine with that given that there is a reasonable probability that wxPython support will be disabled for some platforms until we resolve the gtk3 issues. On 4/10/2018 9:14 AM, Adam Wolf wrote: > Right now, one of the last blockers for the Mac v5 packaging efforts > is wxpython. If it's having i

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Jeff Young
+1 > On 10 Apr 2018, at 14:14, Wayne Stambaugh wrote: > > I'm fine with that given that there is a reasonable probability that > wxPython support will be disabled for some platforms until we resolve > the gtk3 issues. > > On 4/10/2018 9:14 AM, Adam Wolf wrote: >> Right now, one of the last bloc

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Maciej Suminski
In the bug reported for Ubuntu bionic (lp:#1762432) there are three packages installed: - libwxgtk3.0-0v5:amd64 (wxWidgets/GTK2) - libwxgtk3.0-gtk3-0v5 (wxWidgets/GTK3) - python-wxgtk3.0 (wxPython/GTK3) My guess is that some applications may depend on wxWidgets/GTK2, and wxWidgets/GTK3 is simply

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Nick Østergaard
This is because of the wxversion.py. It will then be provided by multiple packages and I don't think it distinguishes different toolkit versions, only multiple wxpython versions. https://wiki.wxpython.org/MultiVersionInstalls 2018-04-10 14:56 GMT+02:00 Wayne Stambaugh : > I wonder why they coul

Re: [Kicad-developers] wxPython-gtk3 woes

2018-04-10 Thread Nick Østergaard
So many distros have wxwidgets with gtk2 and gtk3, but now most upgrade wxpython to gtk3. 2018-04-10 15:36 GMT+02:00 Nick Østergaard : > This is because of the wxversion.py. It will then be provided by multiple > packages and I don't think it distinguishes different toolkit versions, > only multi