Fix Windows installs with Python 2.7 not located in the PATH variable #55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The fix addresses the situation where Python 2.7 is not located in the Windows
PATHenvironmental variable. In my situation I have Python 3.3 located inPATHand, therefore, Maltego transforms fail to execute stating that thecanaripackage is not installed.The fix works by first checking if the script's parent directory contains the
python.exeexecutable and, if it does, uses this executable rather than the one located inPATH.For Windows installations, the Python directory structure is:
This way,
canari.batwill check if<root install>\Python.exeexists, and if it does, execute that version of Python. If this executable doesn't exist, the Python version located in thePATHis executed.