I ran into an issue with matplotlib's build system in bug 479970, which caused me to have a closer look at what we are doing with wxpython. By using alternatives.eclass, the following symlinks get created: /usr/lib/python2.7/site-pacakges/wx.pth -> wx.pth-HIGHEST_VERSION /usr/lib/python2.7/site-packages/wxversion.py -> wxversion.py-HIGHEST_VERSION This creates a couple of problems: 1. When a python package depends on a specific wxpython slot, it actually ends up getting the highest installed version of wxpython. 2. When all versions of wxpython are unmerged, we may end up leaving behind stale wxversion.py[co] files if root ever imported that module. I would propose that we unslot dev-python/wxpython. Are there any objections from the wxwidgets team?
Hmm... actually reading through wxversion.py, point #1 is not the issue I thought it was. wxversion.py is specifically designed to deal with this. We still need to figure out a way to deal with the orphaned py[co] files.
Mike, is this still a thing after more than 10 years now with current (wx)python implementation in Gentoo? Or do you want to close this?
