[Python-Dev] Mercurial migration readiness (original) (raw)

Georg Brandl g.brandl at gmx.net
Sun Jul 4 13:37:27 CEST 2010

Am 04.07.2010 13:29, schrieb Éric Araujo:

The other risk with history-editing extensions is that they use the merge and rebase machinery to do their work, so they require a clean working directory. Otherwise you may loose uncommitted changes.

That's true.

Not requiring any Mercurial extension to contribute to Python would be a nice policy to lower the entry bar.

That is already defeated by the need for the eol extension (which is now built-in in hg 1.6). Activating mq is something every developer should manage...

Georg

-- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out.

More information about the Python-Dev mailing list