Hackable Mercurial: linker_exe and no-cygwin

Eduard-Cristian Stefan alexandrul.ct at gmail.com
Fri Jun 8 02:21:26 CDT 2012

On Fri, Jun 8, 2012 at 10:00 AM, Adrian Buehlmann <adrian at cadifra.com> wrote:
> Ok, thanks. So, it's needed because of your "different drives" scenario
> (k: versus c:), right?


> On a somewhat unrelated note (and sorry for the repeat, but I think it's
> really handy), I have recently switched to have only one "main" Python
> on my system at C:/python (a Windows 7 symlink) and putting only that
> one on $PATH, switching C:/python to different real Python install
> directories (e.g. C:/Python26_x86 and C:/Python26_x64) with different
> variants of Python as needed (as already mentioned elsewhere in this
> thread).

I have no Python install in $PATH, and the one present is a bare bone install
with no other packages. Beside hackable, every project has its own virtualenv,
PyCharm being of great help with managing them.


More information about the Mercurial-devel mailing list