Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Wed, 02 Sep 2009 20:18:35 +0200] rev 9413
manifest.add(): simplify with iterators and generator expressions
Martin Geisler <mg@lazybytes.net> [Sat, 29 Aug 2009 00:30:03 +0200] rev 9412
color: do all setup in uisetup
Now that extensions are loaded in phases, we are guaranteed to always
find mq in uisetup with extensions.find and we know that the mq
commands are not yet copied into commands.table.
Simon Heimberg <simohe@besonet.ch> [Sun, 16 Aug 2009 00:41:24 +0200] rev 9411
extensions: pass ui arguement to extsetup if accepted
Martin Geisler <mg@lazybytes.net> [Sat, 29 Aug 2009 00:29:16 +0200] rev 9410
extensions: load and configure extensions in well-defined phases
Extensions are now loaded with a call-graph like this:
dispatch._dispatch
extensions.loadall
extensions.load
# add foo module to extensions._extensions
extensions.load
# add bar module to extensions._extensions
foo.uisetup(ui)
bar.uisetup(ui)
foo.extsetup()
bar.extsetup()
commands.table.update(foo.cmdtable)
commands.table.update(bar.cmdtable)
hg.repository
foo.reposetup(ui, repo)
bar.reposetup(ui, repo)
The uisetup calls could easily be moved out to dispatch._dispatch, but
have been kept in extensions.loadall since at least TortoiseHg calls
extensions.loadall and expects it to call uisetup.
The extensions.load function called uisetup. It now has an unused ui
argument which has been kept for backwards compatibility.
Martin Geisler <mg@lazybytes.net> [Fri, 28 Aug 2009 22:14:04 +0200] rev 9409
highlight: move code from module top-level into extsetup
Martin Geisler <mg@lazybytes.net> [Fri, 28 Aug 2009 20:53:03 +0200] rev 9408
run-tests: standardize on --foo instead of -f/--foo
We write -f/--foo in Mercurial help texts (docstrings), but I think it
looks strange in error messages.