Peter Otten wrote:
norseman wrote:
This was sent 5/19/09 and as yet has received no comments.
I'm resending just in case a new reader might have an answer.
If you had posted two tiny scripts demonstrating your problem instead of the
longwinded explanation I might have tinkered.
Peter
--------------------------
Since it got lost:
Python 2.5.2 with Tkinter in the download package
Linux Slackware 10.2
That's one of the problems - with Tkinter you don't get tiny files. :)
I have kept working on this and now have it to the point that sending TO
the child w/Tkinter works. Getting messages from the child now shows
that the flush() is not taking place in timely fashion. ALL print
statements FROM child do now flush and are shown correctly, but only
when the child terminates.
Question now is how to force a flush of stdout while the program is
running with tkinter in use.
tkinter section is print "string"
or sys.stdout.write("string")
sys.stdout.flush() fails totally
I don't care how it's flushed as long as it works on whatever machine
python runs on.
NOTE: program runs perfectly on both Linux and Windows XP Pro when run
from the keyboard. But not from another python program that wants the
phone line connected. (stdin/stdout) Gee... There is never a County
Lineman when needed is there Glen? :)
Steve
--
http://mail.python.org/mailman/listinfo/python-list
