Gentoo's changes to add version number to various wxWidgets-related files once again break things: this time, wxPython's "wxaddons" module is completely broken -- it is renamed to wxaddons-2.6 or wxaddons-2.8 (which isn't even a valid Python module name!) by the ebuilds, but alternatives_auto_makesym is *not* used to manage it. Obviously, this means "import wxaddons" now fails on Gentoo. Reproducible: Always Actual Results: $ python -c 'import wx ; import wxaddons' Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: No module named wxaddons $ Expected Results: $ python -c 'import wx ; import wxaddons' $
i'm starting to wonder how on earth different wxpython versions are meant to be installed on the same machine if half the files overwrite one another. :P will alternatives_auto_makesym work in this case? ie. will "python -c 'import wxversion; wxversion.select("2.6"); import wx; import wxaddons'" work when wxaddons is symlinked to wxaddons-2.8?
(In reply to comment #1) > i'm starting to wonder how on earth different wxpython versions are meant to > be installed on the same machine if half the files overwrite one another. :P Well, there's no reason to use any other wxversion than the latest one, for example... > will alternatives_auto_makesym work in this case? It looks like 2.8's version is strict superset of 2.6's. If you don't want to take the risk, then moving wxaddons directory under [all of] version-specific directories for given version (wx-2.6-gtk2-unicode, wx-2.6-gtk2-ansi, ...) should be safe -- the latest one will be picked without wxversion and specific version if you use wxversion.
Upstream commentary: http://lists.wxwidgets.org/cgi-bin/ezmlm-cgi?12:mss:3763:200803:ojmaacoenpieocelapee
(In reply to comment #2) > (In reply to comment #1) > > i'm starting to wonder how on earth different wxpython versions are meant to > > be installed on the same machine if half the files overwrite one another. :P > > Well, there's no reason to use any other wxversion than the latest one, for > example... which is why we symlink to the latest version. this doesn't work for everything of course, which you've encountered. i've moved wxaddons to the versioned directories. thanks for the suggestion and sorry about the breakage.
