I like wxPython. wxPython 4.0 works for me also.
they are the same thing
I think Robi is currently proposing:
wxPython -- version 4.*
rather than making the version part of the name: wxPython4
so one would go to PyPi or whereever and look for wxPython, and probably do:
pip install wxpython
or
pip install wxpython>=4
would get you Phoenix, and
pip install wxpython<4
would get you "Classic" -- if it worked at all.
Similarly for conda.
The only reason I can see from moving away from the well known wxPython
brand, is if the brand sucks or has baggage.
I think the brand is strong, but does now have some baggage, due to
late-coming support for Python3
But I think that will go away fast once we get wxPython 4.0 released!
Who is your target audience? Who are you trying to attract?
- Existing wxPython users?
- Uses of other GUI frameworks?
- New users with looking for their first GUI framework?All of the above? I think if it was only new users, then we couldn't not
worry about the version confusion, etc, and could even have a new name.
But there is a LOT of history here -- second to Numeric, wxPython is the
key package that brought me to Python over 15 years ago!
NOTE, there should probably be something like:
wx.wxWidgets_version
Available in the package if we are going to de-couple the wxPython and
wxWidgets version numbers.
-CHB
···
On Fri, Apr 7, 2017 at 2:10 PM, Brendan <brendanjsimon@gmail.com> wrote:
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov