v0.4.3 - Application Incorrectly Loading C Runtime

[Vezzra]

Ok, I'm just trying to implement the OSX solution also for Windows, but ran into the following problem which prevents me from properly testing if this fix works: I can't reproduce this issue on my XP testing machine. There, even if I have Python installed, the FO app correctly uses the Python environment that ships with it. Consequently, I can implement my fix, make sure FO still works on XP, but can't test if it really fixes things on those Windows versions where the issue occurs.

When I'm done I'm going to provide a PR and will also try to provide a special test build.

[Dilvish]

I can't reproduce this issue on my XP testing machine. There, even if I have Python installed, the FO app correctly uses the Python environment that ships with it.

From the threads I had read, it sounded like this problem was especially likely to arise when there had been a prior app also tinkering with the python path. Could you try installing an extra FO copy in a different location (perhaps as freeorion_prime), and then see if you run into trouble?

[Vezzra]

When I'm done I'm going to provide a PR and will also try to provide a special test build.

Done.

Pull request.

Special test build.

@Buzz and MaiZure: Can you install the special test build on your machines and report back? Pls also provide the log files (freeoriond.log and AI_*.log).

[Vezzra]

Could you try installing an extra FO copy in a different location (perhaps as freeorion_prime), and then see if you run into trouble?

Yup, will do.

[Vezzra]

From the threads I had read, it sounded like this problem was especially likely to arise when there had been a prior app also tinkering with the python path. Could you try installing an extra FO copy in a different location (perhaps as freeorion_prime), and then see if you run into trouble?

Ha! Yes, that reproduced the problem. I installed last weeks test build into a different location, ran it, and the logs clearly showed that FO didn't use the bundled Python environment, but the local Python installation. The module search path contained a mixture of both environments, which of course promises trouble.

I then installed the version containing my fixes into that extra location, ran it - and voilà, FO uses the bundled Python again. Looks promising

Buzz, MaiZure, I'd like to hear back from you, if the special test build fixes the issue for you.

[Dilvish]

I then installed the version containing my fixes into that extra location, ran it - and voilà, FO uses the bundled Python again. Looks promising

Glad to hear it; good job.

[MaiZure]

Uninstalled the regular FO and installed the test build - it works right out of the box without issue.

Much appreciated!

[Vezzra]

Uninstalled the regular FO and installed the test build - it works right out of the box without issue.

Perfect. Patch has already been merged into master, so the current and future test builds should work for you too.