Enabling HgFlow in SourceTree for Windows: “abort: No module named ConfigParser!” error message with “flow: Flow was already initialized for workspace:”
Posted by jpluimers on 2014/02/20
When you get the below error when adding an HgGlow with SourceTree, then do one of these:
- Switch SourceTree to use the internal Mercurial library (which does contain ConfigParser; hgflow depends on it, but it is not shipped with Mercurial any more).
- Install the latest Mercurial command line download for Windows, then add ConfigParser (which is a pain).
Short error message:
hg flow -y -f init
abort: No module named ConfigParser!
Full error message (the middle line is funny “flow: Flow was already initialized for workspace:”):
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| hg flow -y -f init | |
| abort: No module named ConfigParser! | |
| flow: Flow was already initialized for workspace: | |
| Completed with errors, see above. |
Ultimately, hgflow should fix yinwm / hgflow / issues / #8 – Failing on Windows Binary version, but they haven’t for almost 3 years now.
–jeroen
The Wiert Corner - irregular stream of stuff 
Leave a comment