Fix multiple open issues

[Kiyotoko]

• Rename python files (run_seekers and run_python)
• Added os to released archive file names (linux and win32)
• Fix parser argument names
• Split seeker types into multiple files

[Kiyotoko]

This addresses the issues (#46, #76, #77).

[Belissimo-T]

@Kiyotoko Thanks for fixing #46 and #76. I'd like #77 to be fixed in a different way, though.

This is a really big PR 😳. Please, in the future, make sure to submit smaller PRs (ideally one per issue), I won't be reviewing PRs with ~1000 lines changed. I will start looking over the code now.

[Belissimo-T]

This needs lots of changes still, especially regarding the imports. I'd also like to revert 94bbd87, for now.

[Belissimo-T]

I'm working on it. Will amend this PR in a bit.

[Belissimo-T]

The way it is now, is ok. But...

Honestly, I hate that seekers_types is split up.
To start, I dislike the constant need of switching between numerous files. Next, because everything is in different files, you always need lots of imports (This PR adds 150 LOC, mostly comprising imports!). It complicates the whole architecture. Big files (10^3 LOC) aren't inherently bad and occur very often in libraries. And because Python import are evaluated at runtime, everything has to namespaced or you get import cycle errors (longer identifiers). Unfortunately these namespaces have same name as local existing local vars, so these need to be renamed, either by shortening (ew) or an ugly trailing undersocore_ (ewwww).

It just doesn't make sense to pull these classes apart; they all conain cross references to each other. This is not Java.

[Kiyotoko]

The way it is now, is ok. But...

Honestly, I hate that seekers_types is split up. To start, I dislike the constant need of switching between numerous files. Next, because everything is in different files, you always need lots of imports (This PR adds 150 LOC, mostly comprising imports!). It complicates the whole architecture. Big files (10^3 LOC) aren't inherently bad and occur very often in libraries. And because Python import are evaluated at runtime, everything has to namespaced or you get import cycle errors (longer identifiers). Unfortunately these namespaces have same name as local existing local vars, so these need to be renamed, either by shortening (ew) or an ugly trailing undersocore_ (ewwww).

It just doesn't make sense to pull these classes apart; they all conain cross references to each other. This is not Java.

To be honest, I can not really understand why you hate the splitup. I can understand your problems with my mistakes (like mixing up the imports). I did many imports with the IDE and should have manually checked it which I did not, so I can understand your view there. I will fix this. However, splitting up the seeker types improves readability, as it no longer requires to search for the class in the complete file. The file seekers_types was over 900 lines long! This clearly oversteps the level of "long library file". I know that in Python AND Java, there are long files with over 4k lines of code, however, many lines are only comments or docstrings, which is NOT the case in seekers_types. As I have already fixed all cycle errors, there is no need to critiseze namespaces. It does make sense to pull theses classes apart, as they are all represent a different part of the game.

[Kiyotoko]

@Belissimo-T Can we merge it?