McMillan Installer and KDE
h_schneider at marketmix.com
Thu Aug 8 19:30:06 CEST 2002
I did another test: I linked the KDE Link with the plain python file and it
So it seems to be an issue with the Installer!
When I have a look at the spec file then console=1 is set ... maybe it's
really an output problem, a forking prob or both ....
Setting it to 0 results in a missing _runw module. Maybe Gordon himself can
help out here ?
"Gerald Klix" <Gerald.Klix at klix.ch> schrieb im Newsbeitrag
news:aitnvc$2bn$02$1 at news.t-online.com...
> I do not use KDE, but I suppose it tracks the process it starts.
> installer unpacks all neccessary shared objects and
> the forks a subprocess, which is probably not tracked and recognised by
> Just a guess,
> "Harald Schneider" <h_schneider at marketmix.com> schrieb im Newsbeitrag
> news:aitj0k$cs9$01$1 at news.t-online.com...
> > Hi,
> > I've created an application with McMillan's installer and wxPython.
> > The app runs fine under Linux / KDE Desktop,
> > - when I start it from a terminal shell,
> > - when I click it directly,
> > - when I create a symbolic link on the desktop
> > But when I create a KDE Link to my application it fails running.
> > It only starts when I check 'Run in Terminal' in the KDE Link
> > Even a
> > os.close(0)
> > os.close(1)
> > os.close(2)
> > sys.stdin.close()
> > sys.stdout.close()
> > sys.stderr.close()
> > did no solve the problem ...
> > Any ideas ?
> > All the best,
> > Harald
More information about the Python-list