Mercurial > hg
comparison tests/test-module-imports.t @ 25498:7a5335ed7e1a
progress: move the singleton logic to the ui module
The use of a singleton for all of progress handling is debatable (because
config may vary). However this is how the extension has been doing it so far.
We move that code into the ui module because this is where is should belong when
progress is moved into core.
| author | Pierre-Yves David <pierre-yves.david@fb.com> |
|---|---|
| date | Sun, 07 Jun 2015 17:26:34 -0700 |
| parents | 46bf4983cf31 |
| children | 1a6a117d0b95 |
comparison
equal
deleted
inserted
replaced
| 25497:93b8b0049932 | 25498:7a5335ed7e1a |
|---|---|
| 29 mercurial/templater.py mixed imports | 29 mercurial/templater.py mixed imports |
| 30 stdlib: parser | 30 stdlib: parser |
| 31 relative: config, error, templatefilters, templatekw, util | 31 relative: config, error, templatefilters, templatekw, util |
| 32 mercurial/ui.py mixed imports | 32 mercurial/ui.py mixed imports |
| 33 stdlib: formatter | 33 stdlib: formatter |
| 34 relative: config, error, scmutil, util | 34 relative: config, error, progress, scmutil, util |
| 35 Import cycle: mercurial.cmdutil -> mercurial.context -> mercurial.subrepo -> mercurial.cmdutil | 35 Import cycle: mercurial.cmdutil -> mercurial.context -> mercurial.subrepo -> mercurial.cmdutil |
| 36 Import cycle: hgext.largefiles.basestore -> hgext.largefiles.localstore -> hgext.largefiles.basestore | 36 Import cycle: hgext.largefiles.basestore -> hgext.largefiles.localstore -> hgext.largefiles.basestore |
| 37 Import cycle: mercurial.commands -> mercurial.commandserver -> mercurial.dispatch -> mercurial.commands | 37 Import cycle: mercurial.commands -> mercurial.commandserver -> mercurial.dispatch -> mercurial.commands |