| Summary: | Under Python 2.4, wxPython fails to install the wx and wxPython directories correctly | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Stephan Sokolow <only_bugzilla_automail.era.ssokolow> |
| Component: | Current packages | Assignee: | Rob Cakebread (RETIRED) <pythonhead> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | python |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Assigning to pythonhead as he's already investigating this issue. Thanks Stephan, fixed in CVS. |
When using Python 2.4, wxPython will fail to install correctly. This happens whether using wxPython 2.4, 2.6, or both (it's slotted) and prevents any use of wxPython. Reproducible: Always Steps to Reproduce: 1. Unmerge all wxPython versions 2. Emerge wxPython 2.4 and/or 2.6 3. Run python 2.4 and type "import wx" or "import wxPython" Actual Results: Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named wx Expected Results: It should have succeeded and prompted for the next line of the program without displaying a message. Further examinations of emerge ouput revealed that the ebuild is placing the wx and wxPython directories into /usr/lib instead of /usr/lib/python2.4/site-packages where they belong. "mv /usr/lib/wx{,Python} /usr/lib/python2.4/site-packages/" can be used as a temporary workaround.