Package: lairucrem
DescriptionLairucremprovides a useful user interface to theMercurialDVCS.It is a text-based interactive interface that helps developpers on
their daily usage of Mercurial. Because it is a text-based interface,
it can be used over ssh tunnels which is helpful when working on a
remote machine.Lairucremdisplays the changeset tree and the patch content of the
focused changeset. You can interactively inspect the repository
history by changing the focused changeset. We put some effort to make
it quite responsive, even on huge repositories whith big patches.Lairucremcan propose a set of actions that can be applied to the
focused changeset, like rebase, update, addremove, etc. A small set of
actions are available in the actual version but later releases will
propose more actions and a plugin system which will allow you to add
your own actions. You won’t have to mess with a complex UI, just the
actions you need.Lairucremuses the command line interface of Mercurial. So it just
performs the commands you commonly run. It activates extensions
(the “official” ones) when there are needed.We still work onlairucrem, fill issues if you think something could
be improved.InstallationSystem wide (administrator privilege required)pipinstalllairucremUser space (no specific privilege required)pipinstall--userlairucremDevelopmentEnvironmentYou may want to usevirtualenvto create an isolated Python environment.virtualenv/path/to/envs/lairucremenvsource/path/to/envs/lairucremenv/bin/activateClone the repository:hgclonehttp://bitbucket.org/aleufroy/lairucremcdlairucremInstall dev dependencies and lairucrem (in development mode):pipinstall-rdev-requirements.txt-e.Testsuite and checksRun the testsuitespy.test--doctest-modules--pylint-qNote: The–pylintoption enables coding standards checks. Take a
look at thepylintrcfile for detailed coding rules used inlairucrem.Test coveragepy.test--doctest-modules--cov=lairucrem--cov-reportterm-missingDocumentation testpipinstalldocutilspythonsetup.py--long-description|rst2html--strict-TricksI’ve addedpytest-xdisttodev_requirements.txtwhich allows
pytest to watch for file system changes with the-foption.Pull requestPlease check the followings before sending your pull request:Add yourself to theCONSTRIBUTORS.txtfile.Check the new feature/fix by add new tests or by adapting existing
tests (test coverage is useful here). If your change does not need
test change, tell it in the commit message.Check that tests are all green, including the–doctest-modulesand–pylintoptions. Note that you can disable falsy warnings
from pylint (with caution) by adding a comment like:#pylint: disable=signature-differsHelp me understand your patch with a few lines of description in the
commit message (but do not translate your code to english :P). This
makes the patch integration easier and quicker than it could be
without it. You can also refer to an existing issue from thetracker– I’m not a github/bitbucket addict, so let the commit
message self sufficient.In the meantime, you can send me a message on twitter (alainleufroy)
or on the #mercurial IRC channel (aleufroy).Project infoLICENSE:http://sam.zoy.org/wtfplsee LICENSE.txtHOME PAGE:http://bitbucket.org/aleufroy/lairucremBUG REPORT:http://bitbucket.org/aleufroy/lairucrem/issuesSponsorsPythonian