On Sat, Oct 25, 2014 at 1:00 AM, Jun Omae <[email protected]> wrote:

> On Sat, Oct 25, 2014 at 4:46 PM, Ryan Ollos <[email protected]> wrote:
> > On Fri, Oct 24, 2014 at 12:25 PM, Dirk Stöcker <[email protected]>
> wrote:
> >>
> >> On Fri, 24 Oct 2014, RjOllos wrote:
> >>
> >>> The releases are available on the TracDownload page and on PyPI.
> >>> Announcement email forthcoming in a few hours.
> >>
> >>
> >> I'd prefer when the source releases e.g. used by easy_install don't have
> >> "\r\n" as line endings and use "\n" instead. It's pretty ugly on Unix
> >> systems.
> >>
> >> Ciao
> >
> >
> > The tar.gz release should have "\n" line endings. The zip release should
> > have "\r\n". So just easy_install using the tar.gz release on Unix.
>
> The easy_install prefers zip archive even if Unix if both tar.gz and
> zip archives exist, like this.
>

The case willneed to be made why we should favor one particular set of line
endings. Supposing "\r\n" causes problems on Unix (I don't know, I've never
noticed any problems), does "\n" not cause any problems on Windows?

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to