wxPython not installing correctly on Slack 12, possible related issues

Trako · 02-03-2008, 10:53 AM

I have been trying to install PlayOnLinux since yesterday to no avail. The configure halts at

Code:

PlayOnLinux v2.0
----------------
Checking python :                               [ Ok ]
Traceback (most recent call last):
  File "/home/trako/programs/playonlinux/python/mainwindow.py", line 22, in <module>
    import wxversion, os, getopt, sys, urllib, signal, socket
ImportError: No module named wxversion

I installed wxPython, and the error persisted. I searched and saw I might need wxGTK, got that, still had the error.

I did a file search for wxversion, and there it was, in the folder where I extracted the wxPython installer, not in the proper place. I reconfigured, remade, and reinstalled several times and it still stays put there.

So... where exactly does wxversion go? Is there an underlying problem with the installer or other scripts if it can't install properly?

By the way, I have Python 2.5.1 if that helps any.

Any help would be appreciated.

BrianK · 02-04-2008, 01:48 PM

Quote:

Originally Posted by Trako

I have been trying to install PlayOnLinux since yesterday to no avail. The configure halts at

Code:

PlayOnLinux v2.0
----------------
Checking python :                               [ Ok ]
Traceback (most recent call last):
  File "/home/trako/programs/playonlinux/python/mainwindow.py", line 22, in <module>
    import wxversion, os, getopt, sys, urllib, signal, socket
ImportError: No module named wxversion

I installed wxPython, and the error persisted. I searched and saw I might need wxGTK, got that, still had the error.

I did a file search for wxversion, and there it was, in the folder where I extracted the wxPython installer, not in the proper place. I reconfigured, remade, and reinstalled several times and it still stays put there.

So... where exactly does wxversion go? Is there an underlying problem with the installer or other scripts if it can't install properly?

By the way, I have Python 2.5.1 if that helps any.

Any help would be appreciated.

All the wxPython (along with all other python modules) go in the site-packages directory for your python install. Typically, this is in /usr/lib/python<version>/site-pacakges. You can put it somewhere else & specify the path to the root of new location by setting the env var PYTHONHOME (which may allow colon notation for specifying two paths - I haven't tried so I can't confirm). As an example, in the path I gave above, PYTHONHOME would be /usr. It follows, then, that if you set PYTHONHOME to "~/", you'll need ~/lib/python2.5/site-packages.

All that said, something else is probably wrong that causing the make to fail & not install these things in the right place. I would look into that first - dist-clean the install dir & re-run configure (watching for errors/warnings), see what the output of make is, run tests (doesn't wxpython have a "make test"?), etc etc.

As I remember, installing wxPython from source is a royal pain. better to do it with a package manager - slack has one of those, doesn't it?

Trako · 02-05-2008, 01:25 PM

I am bouncing between Slack and Kubuntu. Slack pretty much runs the latest version of wine flawlessly with little to no trouble straight from source. Kubuntu ont he other hand has a packag manager but still has trouble running several things that Slack can. I just wish I could find a middle ground, or some way that I can use one or the other, since the prospect of dual booting just do play games in Slack and to do fancy non-game stuff in Kubuntu isn't very appealing.

Slack has slapt-get, which is maintained third-party, not official. Even then, the packages aren't there, Slack is mainly a source-heavy distro.

With every wipe and bounce, I learn more about linux, I'm getting better with installs, libraries, dependencies and source.

I like using source because it's the latest, probably has a lot of bug fixes the package versions don't have, since a lot of packages are outdated by several point releases.

Perhaps my issue lies with trying to adopt the wrong distro. I'd like to have the convenience of package management but also the freedom to use source when I need to.