Golly Python configuration problem

[cgoler2]

Then where is python38.dll?

EDIT by dvgrn: Moved a discussion of a Python related crash in Golly out of the Speed Demonoid thread, since it's not really related to the specific Speed Demonoid script. Has anyone else had similar trouble with Golly freezing when running Python scripts?

[bubblegum]

Then where is python38.dll?

Just get it from https://python.org/downloads/.

[cgoler2]

I downloaded Python 3.9 with Golly 4.0, and the error is still showing up. What path should I enter?

[dvgrn]

I downloaded Python 3.9 with Golly 4.0, and the error is still showing up. What path should I enter?

First make sure that the Python 3.9 that you've downloaded is 64-bit Python -- the installer executable should end with "-amd64", I believe. It looks like python.org is finally linking to a 64-bit installer as the default, but it's worth double-checking anyway.

After that, the path depends on where exactly you've installed Python. My copy of GollyPrefs in an annoyingly secret hidden folder, kind of hard to find,

Code: Select all

C:\Users\{username}\AppData\Roaming\Golly\GollyPrefs

There's a line in my copy of GollyPrefs that says

Code: Select all

python3_lib=C:\Python39\python39.dll

So you'll want a path that looks something like that -- ends with "python39.dll".

HOWEVER, if you chose the default installation location for one of these modern Windows Python installs, then you'll probably have ended up with a horribly long awkward path instead, something like

Code: Select all

C:\Users\{username}\AppData\Local\Programs\Python\Python39\python39.dll

Substitute your own username for "{username}", and actually go and look in that location before you do anything -- see if there's really a "python39.dll" in a "Python39" folder there.

Don't just try typing in random paths into Golly, and definitely definitely don't start copying files called python39.dll from one location to the other. The DLL will work where the Python installer put it; there's no point in making copies anywhere else.

[cgoler2]

That works. Unfortunately it also results in Golly freezing after a Python script is run.

[dvgrn]

That works. Unfortunately it also results in Golly freezing after a Python script is run.

Just to double-check, what is the name of the Python installer executable that you used to install Python 3.9?

[cgoler2]

python-3.9.5-amd64.exe.

[dvgrn]

python-3.9.5-amd64.exe.

Thanks! I'm temporarily out of ideas for what might be causing Golly to freeze. Can you be a little more specific? Does Golly freeze permanently, no matter which Python script you run? Do you see any error messages, or do you just have to close and restart Golly?

Has anyone else had similar trouble with Golly 4.0 freezing when running Python scripts, with 64-bit Python 3.9.5 installed?

[cgoler2]

Close and restart.
Edit: It only freezes after running biggiemac.py. I tested it by running oscar.py on a pre-pre-beehive.

[dvgrn]

Can you be a little more specific? Does Golly freeze permanently, no matter which Python script you run?

[ihatecorderships]

When I enter the path to python39.dll in the popup which shows up when you try to run a python script, Golly just closed by itself. I have 64-bit python and golly. What might be happening?

[otismo]

Thank You to @ dvgrn for re-directing my questions to this the appropriate thread !

( side question to @ dvgrn : ever heard a band from Madison, WI - now based in Chicago - called Slow Pulp ? find myself listening a lot lately... )

what version python does Goldtiger997's greyship synth script need ?

I may have two, a 2- and a 3-, on my system...

back later with a full issue report -

Thanks !

[dvgrn]

what version python does Goldtiger997's greyship synth script need ?

I may have two, a 2- and a 3-, on my system...

Python 2 is pretty much no longer used to run Golly scripts, since Golly 4.0 and later requires Python 3. Any recently published script, such as the Goldtiger997 Greyship Generator script, is pretty much guaranteed to be Python 3 compatible.

However, we're still in the process of cleaning up and repairing leftover Python 2 scripts, as they get discovered and pointed out (and if they still seem to be useful).