Show More
@@ -375,7 +375,7 b' install some missing tool, or library, a' | |||
|
375 | 375 | Note also, that recent versions of keyring library (since version 12) use Python |
|
376 | 376 | entrypoints to find available backends. Those are incompatible with |
|
377 | 377 | some binary packaging methods (like ``py2app``) and may cause |
|
378 | problems. In particular there were packaged installations of TortoiseHG | |
|
378 | problems. In particular there were packaged installations of TortoiseHG_ | |
|
379 | 379 | which were unable to load keyring backends. See `#61 <https://foss.heptapod.net/mercurial/mercurial_keyring/issues/61/tortoisehg-encounters-unknown-exception>`_ for some more details. |
|
380 | 380 | |
|
381 | 381 | |
@@ -385,7 +385,7 b" Only if this doesn't help, there may be " | |||
|
385 | 385 | |
|
386 | 386 | By far easiest way to have properly working keyring is to use packaged |
|
387 | 387 | binary version (like ``python-keyring`` Ubuntu package, or keyring |
|
388 | bundled with TortoiseHG on some systems). If you pip-installed keyring | |
|
388 | bundled with TortoiseHG_ on some systems). If you pip-installed keyring | |
|
389 | 389 | and it doesn't work, you may consider removing it via ``pip uninstall |
|
390 | 390 | keyring`` and looking for binary package instead. |
|
391 | 391 |
General Comments 0
You need to be logged in to leave comments.
Login now