![]() ![]() The configuration has to be done on the Trac side, there's nothing to do on the Mercurial repository side, except for the fact that the repository should be made accessible as a local repository. You may also want to experiment with Mercurial:HackableMercurial distribution. ![]() Note: Mercurial's library.zip contains pyd-files, which normal Python import can't use (py2exe uses a special importer that allows that), but if you unzip library.zip somewhere and add that directory, it will work on Windows (tested with tracd).Īlternatively, you can install the pre-built Mercurial Python modules from or However, it is not possible to achieve this using PYTHONPATH and PATH: it fails with ImportError: No module named handlers due to library.zip coming in the sys.path before the standard library. ![]() On Windows, it looks like it is possible to re-use the Mercurial library coming from the installer, see this mail. We try to maintain backward compatibility with versions of Mercurial as old as 1.1, up to the latest. You can download Mercurial itself from Hg:Download. The latest stable version is available on PyPI. If you want to get a specific revision, add an svn up -rxxx step to the instructions below, after the checkout. Mercurial itself is released under the GPLv2 license.ĭownload and Installation Releases and compatibility matrix Versionīranches/1.0-stable (1.0.x), branches/1.2-stable (1.2.x), branches/1.4-stable (1.4.x)īranches/1.0-stable (1.0.x), branches/1.2-stable (1.2.x), trunk (1.3.x)īranches/1.0-stable (1.0.x), trunk (1.1.x)Ĭonsult the version table to check which version you need for your version of Trac. log:plugins/0.11/mercurial-plugin, see Trac 0.11 and setting up the plugin for 0.11. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |