Python 3.0a2 is out and some people are working on backports of Python
3.0 features to 2.6. Shouldn't we start to rename the new API functions
and files to their final names before we back merge code to 2.6?
I'm proposing to change the names and files as following. I'm willing to
make the necessar
Note: I cannot speak for git-on-windows (because we don't use it there)...
Our company recently completed a total conversion from svn to git on a large
number of large projects.
At this point, Git:
- Is a very, very active project
- Has a easy-to-learn CLI, with some GUI goodies (the complex par
Christian Heimes schrieb:
> Python 3.0a2 is out and some people are working on backports of Python
> 3.0 features to 2.6. Shouldn't we start to rename the new API functions
> and files to their final names before we back merge code to 2.6?
>
> I'm proposing to change the names and files as followi