Working around a SourceTree Error with Hg Flow

While testing out SourceTree with a current project after watching David Leedy’s great NotesIn9 episode on the subject I came across an error when I first tried to start Hg Flow, so I want to document how to fix it in case anyone else runs into the same problem.

The error I received was, “abort: No module named ConfigParser!”.

SourceTree_ErrorOnHgFlow_1

Fortunately, someone has already documented a fix for this error:

http://blog.omarmohamed.com/fixing-mercurial-problem-abort-no-module-named-configparser/

I followed the steps in that blog post and it worked.

FWIW – When I installed SourceTree, I selected the options to install both Git and Mercurial within it. However, it is important to note that I previously installed Mercurial binaries and have been using that plugin in DDE, so I’m not sure whether that is related.

Advertisements

2 responses to “Working around a SourceTree Error with Hg Flow”

  1. qtzar says :

    in the SourceTree config on the mercurial page switch to using the embedded mercurial and this issue goes away because the embedded mercurial is a few versions older and the ConfigParser python module had not been removed at that stage.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: