For the past few weeks, I've been having a blast hacking away at a pair of scripts for automating some steps of my current photo management workflow that have thus-far been very labour-intensive to perform: Namely, importing/backing up photos and videos from my camera (R5)'s memory card, and doing the same with my phone (Android).
Got an unwanted surprise today trying to run my codebase ("TPMS Studio") using the latest Python (3.11) instead of the 3.7 / 3.8 combos I've been using for the past few years.
Turns out the core team made a breaking change to the behaviour of enums, which breaks our file format + causes the code to crash on startup (assert failures)!
The cause:
`str(eMyEnum.Value_1)` now evaluates to "1" instead of "eMyEnum.Value_1"
(Note: eMyEnum is defined as an IntEnum)
The solution I ended up with was based on:
https://github.com/python/cpython/issues/94763#issuecomment-1313058070
[EDIT: This was the old solution. I have since learned of an even easier fix, from the official docs. See below]
In short, I now do something like:
```
import sys
import enumif sys.version_info >= (3, 11):
# Python 3.11+ hack
class IntEnum(int, enum.Enum):
# Get back old "EnumName.VariantName" str() behaviour
pass
else:
# Use old defines for older Python versions
IntEnum = enum.IntEnum
```
[Latest Update: This solution is easier to use. It comes from the official docs (i.e. example 2)]
```
from enum import Enum, IntEnum
class eMyEnum(IntEnum):
__str__ = Enum.__str__ # <--- That's the key right there
```
Reposting from my original Mastodon posts for easier searchability
This is a quick note on how to get RTree (0.9.7) and PyInstaller (3.4) to play nicely together, so that if you've got a script using RTree (e.g. for example, a script that calls trimesh.proximity.thickness()) that you need to compile into a .exe so that non-technical users can run it as a standalone binary without setting up a Python dev environment first.
These instructions are based on what worked on the project I'm working on, and are only tested with the versions listed on Windows 10. I haven't actually tested this on Linux, since most of the Linux users of this program are already doing a lot more coding work and will have dev environments set up anyway, that it doesn't matter for them.
Hopefully this helps someone else someday.
