I'm not sure if this list or python-dev is appropriate for the more general dvcs discussions - apologies if I got it wrong. There is one issue I'm yet to see addressed - Windows line endings.
When the svn tree is checked out on windows, all text files have \r\n line endings. While many dev tools are capable of working with \n line endings, this quickly becomes inconvenient - eg, my "patch" tool will always insert \r\n line endings, simple commnd-line redirections and dumb editors also will result in mixed or swapped line endings. If we move to a VCS without this support, it becomes trickier to compare, eg, an old svn tree with a new tree on windows as every file differs. While commit hooks etc can go some way to preventing such files from being checked in, it would be much better to avoid the problem in the first place by using native windows line endings, as done by svn.
So I guess the first question is: how much importance do we want to put on that capability?
To the best of my knowledge, bzr's support for this is a few months away. I keep hearing rumours mercurial does support it and I'm just starting work on a mercurial based project, so I may be able to find some answers there - does anyone else have experience with mercurial and windows line endings? I've never used git but again, heard rumours there is some support.
Thoughts?
Mark