[Twisted-Python] Some comments on twisted.news

[Andrew Stribblehill]

Quoting Jp Calderone <exarkun at meson.dyndns.org> (2002-11-01 06:01:45 GMT):
> On Tue, Oct 22, 2002 at 06:49:09PM +0100, Paul Moore wrote:
> > 3. It would be nice if the server handled the translation to CRLF, so
> >    that backends could return data with lines separated by \n, and the
> >    server class would convert that to \r\n. After all, \n is the
> >    "normal" end of line character internal to Python code, and \r\n is
> >    a feature of the NNTP protocol, so the protocol driver should be
> >    responsible for the conversion (IMHO). Of course, this is a
> >    behaviour change, which could break existing backends, so maybe
> >    it's not practical to make this change.
> 
>   I agree that \n would probably be preferable, this was just sloppyness on
> my part in the initial implementation.  I think it could be changed in such
> a way so as not to break existing code, but allow new code to use \n
> (similar to how LineReceiver works), and I think this would be a good thing
> to do.

I posted a patch a few months ago that took any of a number of line
endings. It seemed to get devnulled, and I haven't got a copy any
more but I suspect it's in the list archives. We do *have* list
archives, don't we?

-- 
CROMARTY