En Sat, 19 May 2007 10:31:50 -0300, Stefan Sonnenberg-Carstens
<[EMAIL PROTECTED]> escribió:
> so you'd want this:
>
> f.writelines([x+os.linesep for x in strings])
>
> or something similar.
You would use os.linesep *only* if the file was opened in binary mode -
unusual if you want to write l
On May 19, 2:46 pm, "Gre7g Luterman" <[EMAIL PROTECTED]> wrote:
> "aiwarrior" <[EMAIL PROTECTED]> wrote in message
>
> news:[EMAIL PROTECTED]
>
> > If file.WriteLines( seq ) accepts a list and it says it writes lines,
> > why does it write the whole list in a single line. Be cause of that
> > the r
"aiwarrior" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> If file.WriteLines( seq ) accepts a list and it says it writes lines,
> why does it write the whole list in a single line. Be cause of that
> the reverse of file.writelines(seq) is not file.readlines().
> Are the assumptions
aiwarrior wrote:
> If file.WriteLines( seq ) accepts a list and it says it writes lines,
> why does it write the whole list in a single line. Be cause of that
> the reverse of file.writelines(seq) is not file.readlines().
> Are the assumptions i made correct? If yes why is this so?
>
> I find a fu
aiwarrior schrieb:
> If file.WriteLines( seq ) accepts a list and it says it writes lines,
> why does it write the whole list in a single line. Be cause of that
> the reverse of file.writelines(seq) is not file.readlines().
> Are the assumptions i made correct? If yes why is this so?
>
> I find a f
If file.WriteLines( seq ) accepts a list and it says it writes lines,
why does it write the whole list in a single line. Be cause of that
the reverse of file.writelines(seq) is not file.readlines().
Are the assumptions i made correct? If yes why is this so?
I find a function called writelines not
