Closed EvilSupahFly closed 3 weeks ago
Related to your previous issue in #1093
From my previous evalulation it is probably because python and wxpython were compiled with different compiler flags that expose different symbols.
Damn. I wondered why this error seemed so familiar. But creating a clean new virtual Python environment for a specific version, then grabbing Amulet with PIP in that version was the fix last time, according to the ticket. This time it's not working, which was why I specified pip3 install --isolated --no-cache-dir amulet_map_editor
. I wanted to be doubly sure there was no outside influence. So the problem is my Python environment, I guess, despite running in virtual.
Since this is a repeat of #1093, which was resolved, I'll just close this and go try to sort out my Python situation, and figure out why it's not behaving this time.
Bug Report
As part of my Flatpak troubleshooting, I have been creating and destroying VENVs for testing Amulet in. However, recently PIP Amulet had been crashing the second it starts running with an error reading "undefined symbol: _Py_NegativeRefcount."
Current Behaviour:
In the terminal, I type
python3 -m amulet_map_editor
and it instantly bombs with the above error.Expected behavior:
.... I just want it to run.
Steps To Reproduce:
Install
pythonz
and install Python 3.12.6 into a VENV. Enter said VENV and install Amulet like so:Then attempt to launch Amulet like so:
Environment:
Additional context
The Flatpak Python version is 3.12.6 - that's why I picked it for the VENV, however, for the purposes of this ticket, I tested this by creating various VENVs from Python 3.9, 3.10, 3.11 and 3.12, all with the same result.
Attachments
Terminal output:
Even if I nuke the VENV and start over, I get the exact same result, every time.