Comment 28 for bug 211553

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote : Re: [Bug 211553] Re: wxPython isn't on path in hardy beta

Ok, I've investigated this a bit in Hardy.

David Gaarenstroom wrote:
> Re-fixing? It has never been fixed for Ubuntu 8.04 "Long Time Support"
> and thus wxWidgets apps still don't work out-of-the-box and still need
> the "import wxversion" workaround...

I've just installed python-wxgtk2.8 in a Hardy system (not upgraded from Gutsy)
and importing wx works just fine. So this is not an issue for clean installs
(and you can read that in the bug report too).

> Apparently all Hardy supplied wxWidgets applications are using this
> workaround, or else they would not work AFAIK.

Not really. None of them do (or at least not to workaround this issue). It's in
a few systems where python-wxgtk is broken, and discovering what is causing it
would be a good start (it's not clear to me what's causing it from reading the
report - it's some upgrade issues, but I wonder if it happens for every
gutsy->hardy installation, or for dapper->hardy, or only for people who have
used wxwidgets from wxwidgets.org.

> It is best to use the wxWidgets repository for hardy:
> deb http://apt.wxwidgets.org/ hardy-wx main

That could in fact be the cause of this bug.

AHA!! s/could in fact be/IS/g

I've added that repo to this hardy installation, and upgraded python-wxgtk2.8
(and python-wxversion and libwx{gtk,base}2.8) to the packages from
apt.wxwidgets.org. Importing wx was still working.

Then I've downgraded to the version in Hardy, and it was broken. Why? Because
python-wxgtk2.8 from wxwidgets.org have regular files in
/usr/lib/python2.X/site-packages/wx.pth, but the Ubuntu packages have symlinks
(we need to have it that way to support multiple wx versions).

So I blame wxwidgets.org packages and close the bug as Invalid. Next time think
twice before adding external repositories ;-)

Oh, and reinstalling python-wxversion should fix the issue.

BTW, Devid: I think your debdiff for Hardy was wrong because it would have
'broken' python-wxgtk2.6 (broken as in installing python-wxgtk2.6 provides wx
module, installing your python-wxgtk2.8 provides wx module too, removing
python-wxgtk2.8 no longer provides wx module from python-wxgtk2.6, because it
has removed /usr/lib/python2.X/site-modules/wx.pth which was a regular file in
python-wxgtk2.8).