[Python-modules-team] Bug#478870: Please forward to upstream
frx at firenze.linux.it
Mon Jun 15 20:51:52 UTC 2009
On Sun, 14 Jun 2009 20:33:05 -0400 Varun Hiremath wrote:
> Hi Francesco,
> On Fri, 29 May, 2009 at 11:21:42PM +0200, Francesco Poli wrote:
> > Any progress on this bug?
> > I am still experiencing it with python-traitsgui/3.0.4-1
> > Has it been forwarded upstream?
> I forwarded your report upstream and copied you:
Yes, I saw it.
Thanks a lot, I really appreciate it.
> It seems upstream can't reproduce this bug with wx 2.8, so are you
> sure you are able to reproduce it with wx 2.8 on Debian? If so could
> you please report it on the upstream bug tracker.
I entered in personal e-mail conversation with Gaël (who reads us in
I could not directly reply to the upstream bug tracker, since it
unfortunately does not support interaction via e-mail... :-(
I thought I was using python-wxgtk2.8, just because the Debian package
mayavi2/3.1.0-1 depends on it.
But he explained that this is not necessarily the case.
He suggested me to start mayavi2 and issue the command
'import wx; wx.__version__' inside the IPython shell.
That command told me I was using version 2.6.x.y
Gaël explained that this is caused by the fact that both
python-wxgtk2.8 and python-wxgtk2.6 are installed on my Debian box.
To force the use of python-wxgtk2.8, one can remove python-wxgtk2.6,
if at all possible (i.e.: if no installed package specifically depends
I could remove python-wxgtk2.6.
Now 'import wx; wx.__version__' says 126.96.36.199 and the bug no longer
seems to be reproducible.
Hence, I think I can confirm that the bug is present only when using
python-wxgtk2.6, but not when using python-wxgtk2.8.
We could probably conclude that the bug is in
python-wxgtk2.6/188.8.131.52.2-3 and that it is already fixed in
Gaël also told me that another possible strategy to force the use of
python-wxgtk2.8 is to modify the startup file of mayavi2, and add the
Upstream cannot do so, since it would break compatibility with other wx
I think this strategy could be adopted in the Debian package (as a
Debian-specific patch), since the Debian package currently depends on
python-wxgtk2.8 ... I am not sure that this modification is worth the
annoyance of introducing a Debian-specific patch, though...
In summary, this bug could perhaps be reassigned to
python-wxgtk2.6/184.108.40.206.2-3, with the information that it is already
fixed in python-wxgtk2.8/220.127.116.11-1.1
Otherwise, it could be fixed in mayavi2 by forcing the use of
python-wxgtk2.8, as outlined above.
P.S.: A big thanks to Gaël for all the help he provided for this issue
(I've already replied to him personally, but I am pretty confident that
no secret info is being disclosed here by my public reply to the Debian
New location for my website! Update your bookmarks!
..................................................... Francesco Poli .
GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the Python-modules-team