0

In continuing to research a solution for this question on ServerFault:

https://serverfault.com/questions/221203/mercurial-hook-fails-on-windows

I discovered an interesting and somewhat disturbing thing: I have seem three different versions of Python on my machine (four if you count the "official" version which doesn't appear to have a DLL with it....). Here's shot from my file search tool:

alt text

More Info:

  • I am running Windows 7 64-bit
  • Both the TortoiseHG and the Mercurial directories are on my path, with the Mercurial directory listed first.
  • I have Python 2.6 installed in c:\Python26
  • I have no entry for any type of PYTHON-based environmental variable. (Should I?)

I suspect that this is the source of the my problem from the question above, but I thought I'd ask here, as this is particular issue is a Python deal.

I tried to replace both DLLs with each other, but when I use the one that comes with Mercurial, then TortoiseHg stops working.

It seems to me that "there should only be one" Python on my machine. How do I achieve that?

Improve this question

5 Answers 5

Reset to default
2

For the problem that you mentioned earlier, the mercurial package got installed within python under mercurial home but you are executing scripts under C:\python26. So you need to install and execute your script under mercurial python

As seth mentioned earlier it is perfectly ok to multiple python homes in the same machine but you just to pay attention when installing python libraries to make sure that you are under the right home which means you set the path right before calling python.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

Side note: The Python installation in "C:\Python26" installs its DLL to the Windows directory, in your case "C:\Windows\SysWOW64".

Answering your serverfault question: As you installed Mercurial as standalone version, you'll have to place any packages that are accessed by hooks into Mercurial's library folder (if it has one, could also be "library.zip").

I would recommend you to uninstall the Mercurial standalone version and instead install Mercurial with pip. This makes updates easier and you can use your normal "site-packages" directory for both normal Python libraries and hg hooks.

Improve this answer

5 Comments

Thanks for the answer -- I place the file right into the library.zip file?
@Nick: The "library.zip" can be seen as the site-packages directory, so you can place any package directory in it. But really, I would rather use one global Python installation, and install Mercurial there.
Thanks -- I'm a total python idiot -- how do I "use one global Python installation, and install Mercurial there"?
@Nick: Two alternatives. 1) Just choose "Python package" instead of the installer from the Mercurial download site. 2) Like I described in my answer: Install pip, which will then allow you to install (pip install mercurial) and update (pip install --upgrade mercurial) Mercurial via the command line. As you said you're a Python noob, you may rather want to use alternative 1, but building and using pip might help you understand Python better. Your choice...
Thanks very much. I appreciate your expertise. I'll brave it and try pip. ;-)
1

I would assume that tortoise/mercurial have just embedded their own versions of python to do whatever they need to do.

I wouldn't worry about it, the DLLs won't stomp on each other -- the PATH is the last placed that windows searches to find DLLs.

See: http://msdn.microsoft.com/en-us/library/7d83bc18(v=vs.80).aspx

Improve this answer

Comments

0

Each DLL is for that application. There is only one in your search path so you don't need to worry about conflicts.

Is something not working that prompted you to worry about this??

Your assumption that there should only be one is wrong, each application has bundled a specific version with a fixed API, you can't just drop another in and hope it'll work.

Improve this answer

Comments

0

The Python DLL naming structure only provides the major version and revision numbers. You are probably looking at the DLLs for versions 2.6.1, 2.6.4, 2.6.5, and 2.6.6.

All of this doesn't really matter as long as each application contains its own copy of the python26.dll. Windows will not explore the PATH environment variable if there is a local copy of the file.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.