Trevor, thanks for the detailed explanation. I've now seen that the problem is in python-wxgtk2.4. It sets the wx.pth alternatives in a different way. While python-wxgtk2.4 and 2.6 use it to point /usr/lib/wx/python/wx.pth to wx2.?.pth, python-wxgtk2.4 does a totally different thing and uses it to link /usr/lib/python2.4/site-packages/wx.pth to /usr/lib/wx/python/wx2.?.pth, breaking it.
This likely affects Hardy, Intrepid and Jaunty, and perhaps even Gutsy and Dapper. But I think if we fix it, we should do it just in Hardy and beyond.
Trevor, thanks for the detailed explanation. I've now seen that the problem is in python-wxgtk2.4. It sets the wx.pth alternatives in a different way. While python-wxgtk2.4 and 2.6 use it to point /usr/lib/ wx/python/ wx.pth to wx2.?.pth, python-wxgtk2.4 does a totally different thing and uses it to link /usr/lib/ python2. 4/site- packages/ wx.pth to /usr/lib/ wx/python/ wx2.?.pth, breaking it.
This likely affects Hardy, Intrepid and Jaunty, and perhaps even Gutsy and Dapper. But I think if we fix it, we should do it just in Hardy and beyond.
And there's just one package remaining to be transitioned to wxwidgets2.6 before we can remove wxwindows2.4 from the archive /wiki.ubuntu. com/MOTU/ wx2.4Migration
https:/