Ran Benita

I doubt there's anyone using this code, so I don't think it would warrant any sort of security notification that users should bother with, but if you prepare a PR...

I should have known better that this was going to happen when I replied as I did... If someone can get the notification retracted that'd be best. But I guess...

Note: this semantically conflicts with #243. If #243 is merged, then this PR will need to also update `__hash__`.

@nicoddemus Let's do it! We'll need some way to make it not trigger a PyPI release.

Changed from setup.cfg to pyproject.toml, seems to work. Added it in a separate commit just in case. ~~One final change can be done to eliminate the `tool.setuptools` `py-modules` section by...

There are actually quite a bit of conflicts. Here are warnings that the libxkbcommon Compose implementation spews (with `XKB_LOG_LEVEL=debug` and `en_US.UTF-8` locale): https://gist.github.com/bluetech/ad130434c91ed5809156 There is also one syntax error.

@matthuisman Thanks for providing a reproduction. I bisected the segfault to commit 0dc036035107b213c9b73bf965cbd7356111b85a.

Backtrace: ``` Thread 1 "python" received signal SIGSEGV, Segmentation fault. 0x00007ffff799d901 in _PyInterpreterState_GET () at ./Include/internal/pycore_pystate.h:133 Downloading source file /usr/src/debug/python/Python-3.12.3/./Include/internal/pycore_pystate.h 133 return tstate->interp; #0 0x00007ffff799d901 in _PyInterpreterState_GET () at ./Include/internal/pycore_pystate.h:133...

@matthuisman I will try to see what in pytest has started causing this, however I do not consider the issue to be caused by pytest, because the test does not...

@kavanase Are you able to reproduce this locally? And if so, can you run it under `python -X dev -m pytest` and/or `gdb` to see where the crash happens?