Yes, the commit (for me) broke python3+phoenix. For reference, here are the two versions I see on Debian Buster. I didn't see any way to correlate the Phoenix build with wx version (hence the hard-coded value).
seth@electronics-shop (master)✗ [130] % python3
Python 3.6.7 (default, Oct 21 2018, 08:08:16)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import wx;print(wx.version())
4.0.1 gtk3 (phoenix)
seth@electronics-shop (master)✗ % python
Python 2.7.15+ (default, Aug 31 2018, 11:56:52)
[GCC 8.2.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import wx;print(wx.version())
3.0.2.0 gtk3 (classic)
Hi Orson-
Yes, the commit (for me) broke python3+phoenix. For reference, here are the two versions I see on Debian Buster. I didn't see any way to correlate the Phoenix build with wx version (hence the hard-coded value).
seth@electronic s-shop (master)✗ [130] % python3 wx.version( ))
Python 3.6.7 (default, Oct 21 2018, 08:08:16)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import wx;print(
4.0.1 gtk3 (phoenix)
seth@electronic s-shop (master)✗ % python wx.version( ))
Python 2.7.15+ (default, Aug 31 2018, 11:56:52)
[GCC 8.2.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import wx;print(
3.0.2.0 gtk3 (classic)