From: Kevin A. <al...@se...> - 2001-08-31 15:05:04
|
> From: Guido van Rossum > > The Unix instructions are a bit misleading (am I correct that you > don't use Unix much? :-). Moving the files to "your python21 > directory" makes no sense, they should be moved into > <prefix>/lib/python2.1/site-packages/ where <prefix> defaults to > /usr/local (but may be /usr/bin when Python came as part of your Linux > distribution). > > I *highly* recommend that for the next release you study distutils and > use it to do the installation -- it takes care of the Unix details > too. > > Referring to "double-clicking" samples also reveals your Windows > bias. :-) Okay, the man has spoken. Will some *nix user please provide the complete text required for the installation based on what is at: http://pythoncard.sourceforge.net/getting_started.html Also, what is the appropriate terminology for running a program in *nix from the GUI interface? Surely, you don't have to run Python programs from the command-line? Anyone want to volunteer to do the distutils setup for PythonCard? > (It would be cool if there was a meta-sample that presented a GUI to > run any of the other samples, optionally specifying the command line > options, and with an option to view the source of each sample. Have > you seen the wxPython demo? Very slick!) Anyone up for doing this? The programs need to be launched as their own independent program/process, so you probably need to use os.spawnv() on Windows (though 'start' may also work), and os.fork() or os.execv() on *nix. The 'Launcher.py' program in Mark Lutz's Programming Python 2nd Edition shows how to do this and I'm sure there are similar examples elsewhere. ka |