PEP 374: move section on final decision up.
This commit is contained in:
parent
ecb4918ea8
commit
a3320d9fed
54
pep-0374.txt
54
pep-0374.txt
|
@ -97,6 +97,33 @@ to be used. If this happens, this PEP will be revisited and revised in
|
||||||
the future as the state of DVCSs evolves.
|
the future as the state of DVCSs evolves.
|
||||||
|
|
||||||
|
|
||||||
|
Chosen DVCS
|
||||||
|
===========
|
||||||
|
|
||||||
|
At PyCon 2009, a `decision
|
||||||
|
<http://mail.python.org/pipermail/python-dev/2009-March/087931.html>`_
|
||||||
|
was made to go with Mercurial.
|
||||||
|
|
||||||
|
The choice to go with Mercurial was made for three important reasons:
|
||||||
|
|
||||||
|
* According to a small survey, Python developers are more interested in
|
||||||
|
using Mercurial than in Bazaar or Git.
|
||||||
|
|
||||||
|
* Mercurial is written in Python, which is congruent with the python-dev
|
||||||
|
tendency to 'eat their own dogfood'.
|
||||||
|
|
||||||
|
* Mercurial is significantly faster than bzr (it's slower than git, though
|
||||||
|
by a much smaller difference).
|
||||||
|
|
||||||
|
* Mercurial is easier to learn for SVN users than bzr.
|
||||||
|
|
||||||
|
Although all of these points can be debated, in the end a pronouncement from
|
||||||
|
the BDFL was made to go with hg as the chosen DVCS for the Python project. A
|
||||||
|
detailed plan for the migration strategy has been deferred to `PEP 385`_.
|
||||||
|
|
||||||
|
.. _PEP 385: http://www.python.org/dev/peps/pep-0385/
|
||||||
|
|
||||||
|
|
||||||
Terminology
|
Terminology
|
||||||
===========
|
===========
|
||||||
|
|
||||||
|
@ -1448,30 +1475,3 @@ color-codes the information.
|
||||||
|
|
||||||
XXX ... usage on top of svn, filling in `Coordinated Development of a
|
XXX ... usage on top of svn, filling in `Coordinated Development of a
|
||||||
New Feature`_ scenario
|
New Feature`_ scenario
|
||||||
|
|
||||||
|
|
||||||
Chosen DVCS
|
|
||||||
===========
|
|
||||||
|
|
||||||
At PyCon 2009, a `decision
|
|
||||||
<http://mail.python.org/pipermail/python-dev/2009-March/087931.html>`_
|
|
||||||
was made to go with Mercurial.
|
|
||||||
|
|
||||||
The choice to go with Mercurial was made for three important reasons:
|
|
||||||
|
|
||||||
* According to a small survey, Python developers are more interested in
|
|
||||||
using Mercurial than in Bazaar or Git.
|
|
||||||
|
|
||||||
* Mercurial is written in Python, which is congruent with the python-dev
|
|
||||||
tendency to 'eat their own dogfood'.
|
|
||||||
|
|
||||||
* Mercurial is significantly faster than bzr (it's slower than git, though
|
|
||||||
by a much smaller difference).
|
|
||||||
|
|
||||||
* Mercurial is easier to learn for SVN users than bzr.
|
|
||||||
|
|
||||||
Although all of these points can be debated, in the end a pronouncement from
|
|
||||||
the BDFL was made to go with hg as the chosen DVCS for the Python project. A
|
|
||||||
detailed plan for the migration strategy has been deferred to `PEP 385`_.
|
|
||||||
|
|
||||||
.. _PEP 385: http://www.python.org/dev/peps/pep-0385/
|
|
||||||
|
|
Loading…
Reference in New Issue