I changed that and the writelines and I am very close now. thanks.
Dennis Lee Bieber wrote:
> On 1 Dec 2006 17:24:18 -0800, "[EMAIL PROTECTED]"
> <[EMAIL PROTECTED]> declaimed the following in comp.lang.python:
>
> > data = sys2.stdin.readlines()
>
> And what do you expect to read from
It is left over from the example I stold it from, I remove it and see
if that helps.
Dennis Lee Bieber wrote:
> On 1 Dec 2006 17:24:18 -0800, "[EMAIL PROTECTED]"
> <[EMAIL PROTECTED]> declaimed the following in comp.lang.python:
>
> > data = sys2.stdin.readlines()
>
> And what do you ex
I never see anything from print(data). The example I tried to adapt
using readlines may be a little old or something. I did close all the
files to prevent problems when I figure out what is wrong with what I
have.
John Machin wrote:
> You say "I am sure the readlines code is crashing it." I ca
You say "I am sure the readlines code is crashing it." I can't imagine
how you can be sure of anything, but yes, it is a possibility that
sys.stdin.readlines() might behave strangely when called from a GUI
kit. Why from sys.stdin anyway?
You have two *known* definite problems (not closing your out
John Machin wrote:
> [EMAIL PROTECTED] wrote:
> > I am writing out zero byte files with this (using python 2.5). I have
> > no idea why I am having that problem
>
> Which output file(s) do you mean, temp.orc or temp.sco or both?
> Two possible causes outlined below.
>
> > I am also looking for an
[EMAIL PROTECTED] wrote:
> I am writing out zero byte files with this (using python 2.5). I have
> no idea why I am having that problem
Which output file(s) do you mean, temp.orc or temp.sco or both?
Two possible causes outlined below.
> I am also looking for an example
> of readlines where I ca
