I’m evaluating wxPython (Phoenix) for an upcoming long term project, but am a little nervous recommending it. There hasn’t been a lot of activity on the library over the last year or so. I know the principle developer, Robin Dunn, has been busy on other things, and I’m afraid this might continue indefinitely. Similarly, Andrea Gavana (infinity77) used to be a very active developer, but I haven’t seen any activity from him in a long time. Nor am I reassured when I see blog posts from companies discouraging wxPython’s use for new development.
I’m not accusing Robin or Andrea. I respect their freedom to do whatever they want. That’s OK. And I’m thankful for all the work done. I’m just desperately trying to gauge the future of wxPython (Phoenix), but having trouble. Does anyone have any insight into the future of Phoenix, say over the next two years or so?
Please have a look at the commit’s:
I don’t know why Jonathan March is not mentioning wxPython 3.0.2, a
lot newer release then 2.8. or 2.9.
A cloning tool would help:)
Werner
···
Hi,
On 3/31/2015 14:46, Const wrote:
I'm evaluating wxPython (Phoenix) for an upcoming long term
project, but am a little nervous recommending it. There
hasn’t been a lot of activity on the library over the last
year or so.
I know the principle developer, Robin Dunn, has been busy
on other things, and I’m afraid this might continue
indefinitely. Similarly, Andrea Gavana (infinity77) used to
be a very active developer, but I haven’t seen any activity
from him in a long time. Nor am I reassured when I see blog
posts from companies discouraging wxPython’s use for new
development.
I'm not accusing Robin or Andrea. I respect their freedom
to do whatever they want. That’s OK. And I’m thankful for all
the work done. I’m just desperately trying to gauge the future
of wxPython (Phoenix), but having trouble. Does anyone have
any insight into the future of Phoenix, say over the next two
years or so?
I’ve noticed a burst of activity lately; that’s encouraging.
I know the principle developer, Robin Dunn, has been busy
on other things, and I’m afraid this might continue
indefinitely. Similarly, Andrea Gavana (infinity77) used to
be a very active developer, but I haven’t seen any activity
from him in a long time. Nor am I reassured when I see blog
posts from companies discouraging wxPython’s use for new
development.
I don't know why Jonathan March is not mentioning wxPython 3.0.2, a
lot newer release then 2.8. or 2.9.
Comments like “Qt is a much higher priority for an every-increasing proportion of our users” and “we recommend QT for all new development” kind of scared me. I’m considering Qt (PyQt/PySide), but as far as I can determine, the LGPL v3 license precludes use in proprietary software if I ever want to claim IP (e.g. patent) on my code.
···
On Tuesday, March 31, 2015 at 10:59:08 AM UTC-2:30, werner wrote:
On 3/31/2015 14:46, Const wrote:
I'm not accusing Robin or Andrea. I respect their freedom
to do whatever they want. That’s OK. And I’m thankful for all
the work done. I’m just desperately trying to gauge the future
of wxPython (Phoenix), but having trouble. Does anyone have
any insight into the future of Phoenix, say over the next two
years or so?
According to their license doc (Qt Licensing | Qt 5.15), it sounds like you just have to pay for an “Enterprise, Professional, and Indie Mobile” license to be able to create proprietary code.
Mike
···
On Tuesday, March 31, 2015 at 10:11:50 AM UTC-5, Const wrote:
On Tuesday, March 31, 2015 at 10:59:08 AM UTC-2:30, werner wrote:
Hi,
On 3/31/2015 14:46, Const wrote:
I'm evaluating wxPython (Phoenix) for an upcoming long term
project, but am a little nervous recommending it. There
hasn’t been a lot of activity on the library over the last
year or so.
I’ve noticed a burst of activity lately; that’s encouraging.
I know the principle developer, Robin Dunn, has been busy
on other things, and I’m afraid this might continue
indefinitely. Similarly, Andrea Gavana (infinity77) used to
be a very active developer, but I haven’t seen any activity
from him in a long time. Nor am I reassured when I see blog
posts from companies discouraging wxPython’s use for new
development.
I don't know why Jonathan March is not mentioning wxPython 3.0.2, a
lot newer release then 2.8. or 2.9.
Comments like “Qt is a much higher priority for an every-increasing proportion of our users” and “we recommend QT for all new development” kind of scared me. I’m considering Qt (PyQt/PySide), but as far as I can determine, the LGPL v3 license precludes use in proprietary software if I ever want to claim IP (e.g. patent) on my code.
I’ve noticed a burst of activity lately; that’s encouraging.
I know the principle developer, Robin Dunn, has been busy
on other things, and I’m afraid this might continue
indefinitely. Similarly, Andrea Gavana (infinity77) used to
be a very active developer, but I haven’t seen any activity
from him in a long time. Nor am I reassured when I see blog
posts from companies discouraging wxPython’s use for new
development.
I don't know why Jonathan March is not mentioning wxPython 3.0.2, a
lot newer release then 2.8. or 2.9.
Comments like “Qt is a much higher priority for an every-increasing proportion of our users” and “we recommend QT for all new development” kind of scared me. I’m considering Qt (PyQt/PySide), but as far as I can determine, the LGPL v3 license precludes use in proprietary software if I ever want to claim IP (e.g. patent) on my code.
According to their license doc (http://doc.qt.io/qt-5/licensing.html), it sounds like you just have to pay for an “Enterprise, Professional, and Indie Mobile” license to be able to create proprietary code.
Comments like "Qt is a much higher priority for an every-increasing
proportion of our users"
Are you writing an application where the users of it will be using it to do
GUI development, or are you dependent on the Enthought Python Distribution?
If not, then this statement in of itself probably has no bearing on your
application, unless you take it as a) an indicator that QT itself is a
significantly more robust community and b) that such robustness will matter
non-negligibly to your application's development. I don't think (a) and (b)
are sure bets based on one Python distribution maintainer's response to a
blog post comment.
and "we recommend QT for all new development" kind of scared me.
In this case, he recommends it because of a very specific problem:
incompatibility for 64 bit OSX users of the Enthought Python Distribution
(EPD) who want to develop GUI apps using that EPD ecosystem, for which they
are not prioritizing updating to a now-rather-outdated version of wxPython
(2.8). But I don't think anyone on this list would recommend one start a
wxPython project using wxPython 2.8 at this point. In fact, since you're
interested in Phoenix, this point is irrelevant.
As to how Phoenix is going to go in the next two years, my general view
based on some years of observing various open source projects (or almost
any project, really) is: there is no way to really ever know...or often
even really estimate all that well. Werner gave about as good an indicator
as one can have, which is quantification of recent efforts--which is *very*
encouraging (thanks, Robin!).
···
On Tue, Mar 31, 2015 at 11:11 AM, Const <caleb.constantine@gmail.com> wrote:
Comments like “Qt is a much higher priority for an every-increasing proportion of our users”
Are you writing an application where the users of it will be using it to do GUI development, or are you dependent on the Enthought Python Distribution? If not, then this statement in of itself probably has no bearing on your application, unless you take it as a) an indicator that QT itself is a significantly more robust community and b) that such robustness will matter non-negligibly to your application’s development. I don’t think (a) and (b) are sure bets based on one Python distribution maintainer’s response to a blog post comment.
It’s (a) and (b).
and “we recommend QT for all new development” kind of scared me.
In this case, he recommends it because of a very specific problem: incompatibility for 64 bit OSX users of the Enthought Python Distribution (EPD) who want to develop GUI apps using that EPD ecosystem, for which they are not prioritizing updating to a now-rather-outdated version of wxPython (2.8). But I don’t think anyone on this list would recommend one start a wxPython project using wxPython 2.8 at this point. In fact, since you’re interested in Phoenix, this point is irrelevant.
As to how Phoenix is going to go in the next two years, my general view based on some years of observing various open source projects (or almost any project, really) is: there is no way to really ever know…or often even really estimate all that well. Werner gave about as good an indicator as one can have, which is quantification of recent efforts–which is very encouraging (thanks, Robin!).
True. I’m just trying to get something, anything, to improve my estimate (as you put it).
···
On Tuesday, March 31, 2015 at 5:46:16 PM UTC-2:30, Che M wrote: