diff 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
line wrap: on
line diff
--- a/tests/test-module-imports.t	Sun Jun 07 17:19:20 2015 -0700
+++ b/tests/test-module-imports.t	Sun Jun 07 17:26:34 2015 -0700
@@ -31,7 +31,7 @@
      relative:  config, error, templatefilters, templatekw, util
   mercurial/ui.py mixed imports
      stdlib:    formatter
-     relative:  config, error, scmutil, util
+     relative:  config, error, progress, scmutil, util
   Import cycle: mercurial.cmdutil -> mercurial.context -> mercurial.subrepo -> mercurial.cmdutil
   Import cycle: hgext.largefiles.basestore -> hgext.largefiles.localstore -> hgext.largefiles.basestore
   Import cycle: mercurial.commands -> mercurial.commandserver -> mercurial.dispatch -> mercurial.commands