Remove a redundant section.
This commit is contained in:
parent
41068ada83
commit
110585a7fa
25
pep-0374.txt
25
pep-0374.txt
|
@ -97,31 +97,6 @@ to be used. If this happens, this PEP will be revisited and revised in
|
|||
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 four 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.
|
||||
|
||||
|
||||
Terminology
|
||||
===========
|
||||
|
||||
|
|
Loading…
Reference in New Issue