On 10/20, Marcin Kasperski wrote: > > Windows is hard. If you want to install them by pip and make them just work, > > you'll need a workable Python "mercurial" and "tortoisehg" packages. I don't > > think it is worth trying because common Windows users don't have Python. > > I ended up documenting how to clone (and implementing in my extension > trick ???if you can't import helper module, look whether it is available > in the same directory or appropriately named neighbour???). > > Still, it would be fairly nice, if Windows TortoiseHg could bundle some > kind of properly configured pip, so one could > tortoisehg-pip some-package > or maybe > thg pip some-package > and have this package visible in Tortoise Mercurial. > For non-bundled plugins usability it would be incredibly friendlier. > > Or, if not that, maybe Windows Tortoise could at least handle some > site-packages directory (say C:\Program Files\Tortoise HG\site-packages > or sth like that)? This would open possibility of writing separate > ???install to tortoise"" tool.
You can use a Mercurial extension to add a folder to the thg Python system path. see https://bitbucket.org/tortoisehg/thg-winbuild/downloads/insertpath.py And https://bitbucket.org/tortoisehg/thg/wiki/libsvn for an example of how it is used. You could add this to a local site-packages folder, but you have to be careful none of it conflicts with the packages shipped with thg. -- Steve Borho ------------------------------------------------------------------------------ _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
