hgview #117624 hgview is not longer usable standalone [validation pending]
dropping sys.path manipulation dropped the ability to use hgview without extra installation process.
User roar | |
| priority | normal |
|---|---|
| type | bug |
| done in | 1.8.0 |
| load | 0.500 |
| load left | 0.000 |
| closed by | #cf93defad8a8 [launcher] load hgviewlib manually if standalone (closes #117624) |
| patch | [launcher] find hgviewlib automatically (closes #117624) [applied] |
Comments
-
2013/01/28 10:43, written by aleufroy
-
2013/01/28 10:53, written by aleufroy
add commentNote that manipulating the sys.path seems not to be a good approach.
In fact, adding the repository path as first search path results in conflicts with installed packages (especially hgext) while adding it at the last position would not work if hgview is already installed (a.k.a. for people that want to try a newer version).
We shall build the package paths then we shall import them using imp.
The best way is to install hgview. Non-admin users may use ``python setup install --home=$HOME``.
However, if the "standalone" version is really important, the hacked code should take place in dedicated scripts (a.k.a. "bin/hgview_dev" and "hgext/hgview_dev.py").