Installing Nmap on Windows will cause pyscripter to malfunction

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install Nmap (http://nmap.org/dist/nmap-4.90RC1-setup.exe)
2. Run pyscripter

What is the expected output? What do you see instead?
When pyscripter is run, it complains about a Python installation error, but 
no PYTHONPATH or PYTHONHOME environment variable is set, and the registries 
are fine. The editor opens, but whenever python libraries are accessed, an 
error box appears.

What version of the product are you using? On what operating system?
Python Scripter 1.9.9.7 on Windows XP

Please provide any additional information below.
Immediately after uninstalling Nmap, pyscripter worked as usual again.
The Nmap installation may have screwed up something with the path, but I'm 
not exactly sure. I hope this is helpful.

Original issue reported on code.google.com by tgfco...@gmail.com on 8 Jul 2009 at 9:24

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The error is given in
http://code.google.com/p/pyscripter/source/browse/trunk/StringResources.pas

under SPythonInitError

Original comment by tgfco...@gmail.com on 8 Jul 2009 at 9:26

[GoogleCodeExporter]

Nmap must be installing on the system path a pythonxx.dll which is picked by 
PyScripter instead of the one in the standard python distribution.  Modify the 
PATH environment variable so that this does not happen.

Original comment by pyscripter on 1 Sep 2010 at 4:34

• Changed state: Invalid

[GoogleCodeExporter]

Kiriakos:

Can you please explain the reasoning for this? I think I have similar problems 
with TortoiseHG using python26.dll, which is on the system path, yes, but also 
on the system path (and in fact before the TortoiseHG entry) is an official 
python25.dll, and all settings in the windows registry point to this python25 
version. Why does Pyscripter insist on using the python26.dll in such a case?

I know that using the --python25 command line argument to Pyscripter 'solves' 
the issue, but I would like to understand the reasoning. Thanks!

Tgfcoder:

You could try to use the --pythonXX (where XX is the number of your official 
python installation, e.g. --python25) and see if it works (with nmap installed)

Original comment by epposan@gmail.com on 1 Sep 2010 at 8:05

[GoogleCodeExporter]

TortoiseHg (http://code.google.com/p/pyscriptr/issues/detail?id=189) caused 
additional problems by implementing a Shell Extension in Python. So a Python 
dll was loaded in PyScripter via its File Explorer, and this might have been a 
different version than the one PyScripter attempted to use.

PyScripter without any command-line options tries to load the highest version 
of Python it can find in the system path doing the standard system search for 
dlls.  If the found python dll does not have corresponding registry information 
or if the PYTHONHOME environment variable is not defined then it fails.  

You can always direct PyScripter to use a specific version using the --PYTHONxx 
flag and also specify the location of the DLL using the --PYTHONDLLPATH command 
line option.  See http://code.google.com/p/pyscripter/wiki/FAQ for more details.

Original comment by pyscripter on 1 Sep 2010 at 9:42