Dear all,
in GRASS project [1] we are facing to a serious problem with wxPython
due to well known bug [2]. Several our tools are not functional at all
due to this bug. The last version 3.0.2 has been released in November
2014. This bug seems to be fixed 6 months ago [2]. Is there any chance
that wxPython community will be able to release 3.0.3 this year? It
would help us a LOT! Thanks for your work! Martin
[1] http://grass.osgeo.org/
[2] http://trac.wxwidgets.org/ticket/16767
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
Hi,
2016-07-14 20:26 GMT+02:00 Dietmar Schwertberger <maillist@schwertberger.de>:
Is Phoenix an option for you?
Douglas is currently doing a lot of work on lib.plot for Phoenix.
Maybe you should test the latest snapshot whether the fix is in already. If
not, please comment on the pull request at
https://github.com/wxWidgets/Phoenix/pull/117
may be, I was speaking with one colleague of mine, she mentioned that
Phoenix probably lacks PseudoDC. This would be absolute blocker for
us. We use PseudoDC for rendering data. There is also question how
much time it can take to get Phoenix into distributions like Debian. I
would vote for releasing classic as it is now as 3.0.3 at least.
Or is Phoenix not an option?
Then it might be the best to take the classic version, apply the patch and
build it yourself.
Hm, we are trying to support wide range of platforms. It's impossible
for us to build every dependency on our own, sorry. We must relay on
official packages.
I'm not aware of plans for a new build.
That's VERY VERY bad news for us 
Martin
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
Hi,
2016-07-14 21:47 GMT+02:00 Dietmar Schwertberger <maillist@schwertberger.de>:
I don't think that there are licensing problems.
You may import your version right at the start of your software.
Then do something like
sys.modules["wx.lib.plot"] = sys.modules["patched_plot"]
yes, sure, we will do. But it's non-systematic way. Better would be
new wxPython release 
Thanks, Martin
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
W dniu 14.07.2016 o 20:49, Martin Landa pisze:
2016-07-14 20:26 GMT+02:00 Dietmar Schwertberger <maillist@schwertberger.de>:
Is Phoenix an option for you?
Douglas is currently doing a lot of work on lib.plot for Phoenix.
Maybe you should test the latest snapshot whether the fix is in already. If
not, please comment on the pull request at
https://github.com/wxWidgets/Phoenix/pull/117
may be, I was speaking with one colleague of mine, she mentioned that
Phoenix probably lacks PseudoDC. This would be absolute blocker for
us. We use PseudoDC for rendering data. There is also question how
much time it can take to get Phoenix into distributions like Debian. I
would vote for releasing classic as it is now as 3.0.3 at least.
Or is Phoenix not an option?
Then it might be the best to take the classic version, apply the patch and
build it yourself.
Hm, we are trying to support wide range of platforms. It's impossible
for us to build every dependency on our own, sorry. We must relay on
official packages.
I'm not aware of plans for a new build.
That's VERY VERY bad news for us
I have asked a question on a related note in Trac [3], but haven't got a
reply so let me repeat it here:
Having added wxversion.select('2.8') in line 64 of
gui/wxpython/core/globalvar.py to force wxgui to pick version 2.8 I got
rid of the "Required argument 'type' (pos 2) not found" errors in
profile surface map, bivariate scatter plot and histogram of raster map
tools on my box.
I confirmed that all GRASS wxgui uses 2.8.12.1 then, rather than 3.0.2,
which is available on my system as well, with "cat /proc/<pid>/maps",
where <pid> > is the PID of the g.gui.* process.
Can't GRASS use this workaround for the time being? You may also want to
have a look at Glynn's comments in another thread from few years ago [4].
[3] https://trac.osgeo.org/grass/ticket/2558#comment:10
[4] https://lists.osgeo.org/pipermail/grass-dev/2014-October/071137.html
--
Maciej Sieczka
http://www.sieczka.org
Good news, one of the blockers for using wxPython Phoenix (the
completely new version of wxPython supporting Python 3) was solved, so
we can start testing it.
Anna
---------- Forwarded message ----------
From: Dietmar Schwertberger <maillist@schwertberger.de>
Date: Sat, Jul 30, 2016 at 5:06 AM
Subject: Re: [wxPython-users] 3.0.3 ?
To: wxpython-users@googlegroups.com
On 14.07.2016 20:49, Martin Landa wrote:
may be, I was speaking with one colleague of mine, she mentioned that
Phoenix probably lacks PseudoDC. This would be absolute blocker for
Robin has just added PseudoDC to Phoenix.
So it should be in the next snapshots.
Regards,
Dietmar
--
You received this message because you are subscribed to the Google
Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On 03/08/16 13:12, Anna Petrášová wrote:
Good news, one of the blockers for using wxPython Phoenix (the
completely new version of wxPython supporting Python 3) was solved, so
we can start testing it.
Sounds great. Do I understand correctly that the Phoenix API is different from the classic API and thus wxGUI will have to be rewritten for Phoenix ? Or can I just install Phoenix and it should work ?
Moritz
On Wed, Aug 3, 2016 at 9:50 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
On 03/08/16 13:12, Anna Petrášová wrote:
Good news, one of the blockers for using wxPython Phoenix (the
completely new version of wxPython supporting Python 3) was solved, so
we can start testing it.
Sounds great. Do I understand correctly that the Phoenix API is different
from the classic API and thus wxGUI will have to be rewritten for Phoenix ?
Or can I just install Phoenix and it should work ?
I think something in between. It's fairly compatible, so we don't have
to rewrite it but some ifs here and there might be needed. At least
that's my guess.
Moritz