Rweth wrote:
> so afile contains a filename.
> One single aline looks like so:
>''
Beats me where those empty lines come from, it doesn't seem to
happen in nntplib.
Does the same thing happen if you pass .body() a filepointer?
Cheers,
--
Klaus Alexander Seistrup
http://klaus.seistrup.dk/
Klaus Alexander Seistrup wrote:
> Rweth wrote:
>
>>for aline in buf:
>> bufHeal.append(aline.replace('\r\n', '\n'))
>
> What does one single aline look like?
>
>> s.body(id,afile)
>
> Does the 'afile' contain a filename or a filepointer?
>
> Cheers,
>
so afile contains a filename.
O
Rweth wrote:
>for aline in buf:
> bufHeal.append(aline.replace('\r\n', '\n'))
What does one single aline look like?
> s.body(id,afile)
Does the 'afile' contain a filename or a filepointer?
Cheers,
--
Klaus Alexander Seistrup
http://klaus.seistrup.dk/
--
http://mail.python.org/mai
Klaus Alexander Seistrup wrote:
> Rweth wrote:
>
>> I am using nntplib to download archived xml messages from our
>> internal newsgroup. This is working fine except the download
>> of files to the connected server, has extra embedded lines in
>> them (all over the place), from the
>>s.body
Rweth wrote:
> I am using nntplib to download archived xml messages from our
> internal newsgroup. This is working fine except the download
> of files to the connected server, has extra embedded lines in
> them (all over the place), from the
>s.body(id,afile) # body method
The 'linebreak
I am using nntplib to download archived xml messages from our internal
newsgroup. This is working fine except the download of files to the
connected server, has extra embedded
lines in them (all over the place), from the
s.body(id,afile) # body method
Is there any way to employ this library
