Error : "abort: No module named keyring!"

Issue #15 invalid
Brice Dutheil
created an issue

This extension do not seem to work with multiple install of python.

I'm facing similar issue issue as this guy on SO http://stackoverflow.com/questions/5173197/python-import-seems-to-behave-differently-in-mercurial-keyring-py-file

Tough my extension was cloned elsewhere in the path

{{{hgext.mercurial_keyring = ~/work/oss/mercurial_keyring/mercurial_keyring.py}}}

Also Mercurial was installed with Homebrew on OSX. Th hg command refer to the 2.7 python package. {{{libdir = '..//python2.7/site-packages/'}}}

while the python command report version 2.7.1.

As I don't know python at all, you might have some better input than me.

Thx

Comments (2)

  1. Marcin Kasperski repo owner

    mercurial_keyring requires keyring library to be installed within whichever python mercurial uses. If you install it using (proper!) easy_install, keyring library is automatically installed (if missing).

    There is nothing else I can do, resolving problems related to multiple python installations on the machine is not a task simple plugin should (or can) perform. There were some discussions about merging the extension to the mercural core in the past, until it happens one must install all necessary pieces by him(or her) self.

    As I see there are some more detailed suggestions on stackoverflow thread you mentioned, so you can refer to them.

  2. Brice Dutheil reporter

    Hi Marcin

    Thx for the feedback.I didn't use the proper installation as the documentation said I can directly use a path to the python file. I think then the documentation to be improved to say that if you do that you are on your own! ;)

    There is nothing else I can do, resolving problems related to multiple python installations on the machine is not a task simple plugin should (or can) perform

    OK, I understand. Too bad :/

    There were some discussions about merging the extension to the mercural core in the past.

    OK, that would be really cool!

    As I see there are some more detailed suggestions on stackoverflow thread you mentioned, so you can refer to them.

    Yep, but it's somehow a workaround that's why I reported an issue here. Too bad it couldn't be easily fixable.

    Cheers, Brice

  3. Log in to comment