spe woes (Stani's Python Editor)
Terrance N. Phillip
getting it going on Slackware 10.2. What I've done:
Got wxWidgets, configure, make, make install.
Got wxPython (2.6.1.0) from linuxpackages.org, installed
Got spe, did python setup.py install
But something's still missing. When I run spe, I get Spe Error: Please
install the right version of wxPython: 2.6.1.0.
Not too sure where to go from here. Help?
Nick.
BUT WAIT... just tried firing up idle, and did import wxPython. That
bombed with ImportError: libwx_gtk2u_xrc-2.6.so.0: cannot open shared
object file: No such file or directory.
So I'm thinking that maybe the wxPython package I got is corrupt? I'll
try getting a fresh copy. In the meantime, if anyone has any thoughts,
I'd be glad to hear them!
N
MikeReynolds
<snip>
> Got wxWidgets, configure, make, make install.
> Got wxPython (2.6.1.0) from linuxpackages.org, installed
> Got spe, did python setup.py install
>
> But something's still missing. When I run spe, I get Spe Error: Please
> install the right version of wxPython: 2.6.1.0.
>
> Not too sure where to go from here. Help?
>
> Nick.
>
> BUT WAIT... just tried firing up idle, and did import wxPython. That
> bombed with ImportError: libwx_gtk2u_xrc-2.6.so.0: cannot open shared
> object file: No such file or directory.
>
> So I'm thinking that maybe the wxPython package I got is corrupt? I'll
> try getting a fresh copy. In the meantime, if anyone has any thoughts,
> I'd be glad to hear them!
>
> N
wxGTK and wxPython are a major pain to install _properly_ and get a setup
that actually works. I found packages of both that semi work. (both from
linuxpackages.net or through portpkg, can't remember which) By semi work, I
mean most apps that use either or usually work. IIRC the best way to get
an app that uses wxPython to work is download wxPython, and use the wxGTK that
it bundles. It seems that wxPython needs specific versions of wxGTK in order
for it to work. Sorry that I don't have more conclusive answers for you. Just
know that I feel your pain ;-).
It really is unfortunate that wxGTK/wxPython is such a pain to setup as it is
a nice toolkit, and cross-platform to boot. It makes me wonder if the devs
actually want people to use it. I also wonder why people use this toolkit
sometimes. When I do get it working, it works well, but getting to that point..
I wish someone with more expertice would start making slack packs. I don't
think slackBuild scripts can handle wxGTK/wxPython properly. I'm by no means an
expert in that though.
--
Best Regards,
Mike Reynolds
Terrance N. Phillip
>It really is unfortunate that wxGTK/wxPython is such a pain to setup as it is
>a nice toolkit, and cross-platform to boot.
Well, thanks for the reply. I'm glad it's not just me! I was wondering
if the wxPython package from linuxpackages.org _already_ bundles wxGTK,
and I messed things up by building wxGTK separately? (It's just that
the wxPython packages doesn't seem "big" enough. I should explode it
and see what's actually in the thing...)
N
MikeReynolds
I'm pretty sure the linuxpackages package didn't work for me. I think I got
wx* from portpkg, a ports-like system for slackware. I hope someone in the know
reads this thread.
spe.st...@gmail.com
garantuee you for 100% you can install SPE.
About wxPython it might be hard to install if there are no packages
available, but it has a *very* supportive community. So why not pay a
visit to the wxPython mailing list and do a post there. You'll
definitely get help.
Good luck,
Stani
spe.st...@gmail.com
MikeReynolds
Sorry, I meant that the wxGTK/wxPython packages frm linuxpackages didn't work
properly, not the SPE package.
Terrance N. Phillip
> I really want to give this editor a try, but I'm having a real challenge
> getting it going on Slackware 10.2. What I've done:
>
Finally got SPE working. I removed the wxPython package I found at
linuxpackages.net, and instead, followed the instructions I found here:
http://aspn.activestate.com/ASPN/Mail/Message/wxpython-users/3030531
Although the author found the "tone of the list a little frustrating,"
his instructions are nearly bang on. I'll re-post them with a couple of
minor corrections here:
1: Download wxPython source tarball from wxpython.org. This is the
wxWidgets tree, no other source files should be needed (except for
headers & libs for dependent libraries, like mesa for opengl)
2: extract tarball & cd into directory
3: mkdir unicode-debug, cd unicode-debug
4: ../configure --with-opengl --enable-unicode --enable-debug
--enable-debug_flag --enable-debug_info --enable-debug_gdb
Note: author had --enable-unicide, but that can't be right???
5: make && make install && ldconfig
6: cd contrib;make && make install && ldconfig
7: cd ../../wxPython
8: python setup.py install UNICODE=1
Nick.