[Python-Dev] PEP 385: the eol-type issue
dirkjan at ochtman.nl
Wed Aug 5 11:09:44 CEST 2009
On Wed, Aug 5, 2009 at 11:02, Mark Hammond<skippy.hammond at gmail.com> wrote:
> In general I agree - although I think we can enforce a "social contract"
> which puts requirements on people who commit to the Python repository - and
> therefore we can consider the server-side hooks a "secondary" defense. IOW,
> the system (including the social aspects of the system) are setup such that
> the server-side hooks are very rarely called upon.
> With all due respect, I suspect that is because you don't expect to see the
> issue regularly.
I suspect so, too!
> I'm yet to work on a hg repository without mixed line endings. If I
> understand correctly, every such repository would have involved a developer
> checking in locally, than at some point in the future pushing these changes
> upstream. I really really don't want hg to tell me at this final step that
> I need to perform whitespace only fixes purely because I am running Windows.
> I understand we are discussing how win32text can offer that - but I must
> object to your assertion that the situation I described isn't bad when you
> hit it.
I agree it is to be avoided, I'm just saying that I think it will be
exceptional and therefore not a large burden, given other kinds of
defenses we can put in place.
> Actually, I think it is easy to make this problem much easier to understand;
> mandate every platform should use win32text, then start collating the issues
> people, including yourself, will no doubt face. I'm happy to get this ball
> rolling, but again, don't want this left purely in the domain of "it is a
> windows problem" - it isn't.
I'm not sure how win32text will provide anything other than
performance degradation for non-Windows developers, but if there's
functionality to be had, I'm happy to mandate its use on every
More information about the Python-Dev