For anyone who feels the Mac instructions are a bit broken... update Python. New version came out literally 2 days ago (which is probably why I couldn't find it or reference to it or anything) and it works fine. 3.3.5. Open main.py with IDLE. and run it by file menu or by hitting F5. No idea how anyone installed it before March 9, 2014, but it's doable now.
running OSX 10.9.2 and it's just silly.
I'll start by saying there's nothing that actually opens the .py file you gave us. Skipping past that, googling gave me a workaround by using Terminal (console). I run it through there and get a syntax error - it refuses to do anything.
Code:
python
Python 2.7.5 (default, Aug 25 2013, 00:04:04)
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> /Users/HomeFolder/Documents/Paradox\ Interactive/Crusader\ Kings\ II/mod/HIP/main.py
File "<stdin>", line 1
/Users/HomeFolder/Documents/Paradox\ Interactive/Crusader\ Kings\ II/mod/HIP/main.py
^
SyntaxError: invalid syntax
I'd try to make up some files/folders and put them in manually, but there aren't any .mod files anywhere, so I'm at a bit of a loss.
EDIT:
I'm sorry. I may have been a bit harsh on you. While I don't appreciate some of the comments you made and [still] definitely don't appreciate you making blanket statements directing other users to use an alternate, incompatible, and unsupported means of getting the installer to run on Mac OS X when the
bundled HIP readme.txt contains easy, succinct instructions that work out of the box if tried, I was totally unaware at the time of posting my response to you that the OP of this thread hadn't yet been updated to include the Mac OS X install instructions that are in the
HIP readme.txt found in the download archive. Due to forum limitations, only one person (and Paradox moderators) can update that post, and I'm not that person, although I am the guy that spent a great deal of time making OS X / Linux installs work smoothly out of the box (amongst a host of other installer improvements over prior HIP releases) and wrote the bundled instructions for OS X / Linux. The person who can update the OP of this thread will be consequently updating the instructions listed there, which are presently Windows-centric, in about 6 hours.
Consequently, please accept my apologies for my harsh tone. I worked very hard specifically so that users like yourself would be able to enjoy HIP on OS X glitch-free, and it's anathema to the reason I did that to harshly criticize your inability to follow the instructions when you simply overlooked the bundled
HIP readme.txt. You should have seen those instructions in the same post as the download link too, and now that issue will be resolved as soon as the proper individual is available to adapt them to the OP in, as mentioned, 4-6 hours.
Original post:
I'm not sure what instructions you're looking at, because all of your description / quoted code of what you did, including your blanket recommendation of what all our other users do, is
definitely not the same approach the instructions clearly specify in the 'HIP readme.txt' file included in the download archive. Your system-bundled Python-- not the Python from python.org (though that works, in a different way, and incompatibly so)-- was supposed to be used from Terminal, and you were supposed to execute one, single command, which fit upon a single line and required zero modification from the instructions.
The instructions clearly, succinctly explained how to accomplish this with a single copy/paste directly into the Terminal window, followed by hitting ENTER.
You, instead, ran Python in interactive "learning" mode (also known as 'calculator mode') and tried to execute the installer with a custom path by inputting it into the interactive Python language console directly, when Python was expecting you to enter valid Python language syntax, as if you were inputting a Python program by hand. Hence, the error you received initially. You then apparently tried a bunch of other things that you shouldn't, because the HIP installer and package a is a dynamic mod compiler-- not a mod directly.
If you had followed the instructions in 'HIP Readme.txt', the installer would've run without incident. It's somewhat of a happy coincidence for you that despite your upgrade to a theoretically incompatible version of Python (the 3.x series is not compatible with the 2.x series, the latter of which is mandatory-installed on every OS X machine) that the installer still was able to execute without error. That configuration hasn't been tested on OS X, mainly because it involves several unnecessary, relatively convoluted steps added to the process for no gain. Additionally, the fact that you were able to get it to run correctly in the end with Python 3.3 does not guarantee that others who, e.g., make different mod selections or that are installing future versions in your way instead of the instructed way will not encounter incompatibility errors.
I'm glad that you got it working in the end, regardless, but please be careful what you broadcast as the One True Faith to our users for us. We usually respond to user install problems within 15-60 minutes maximum, 24x7. You definitely were in a hurry to get it installed (don't blame you) and thus went on to try a bunch of confusing things rather than give the README a fresh start again, if you did in the first place. That's fine, but it is definitely no grounds to make those sweeping claims and confuse folks.
Sorry to be harsh. Enjoy.
To everybody else on OS X:
Please read and follow the short instructions in the 'HIP Readme.txt' that's extracted directly into your mod folder along with the installer itself in the first step that follows download (extraction/decompression of the .7z file). It works. When you reach the second step further, which was where things went wrong here, just be sure to exactly copy/paste the line of text indicated without any modifications, and you'll be instantly up and running.