[BUG] Class `Intents` received an invalid and unexpected value (Python 3.12.3) about interactions.py

[Scrxtchy]

I put a traceback on it

Traceback (most recent call last):
  File "D:\Scratch\Documents\Git\June\Lib\site-packages\interactions\models\discord\enums.py", line 112, in __call__
    return super().__call__(int_value, names, module=module, qualname=qualname, type=type, start=start)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\...\AppData\Local\Programs\Python\Python312\Lib\enum.py", line 757, in __call__
    return cls.__new__(cls, value)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\...\AppData\Local\Programs\Python\Python312\Lib\enum.py", line 1179, in __new__
    raise exc
  File "C:\Users\...\AppData\Local\Programs\Python\Python312\Lib\enum.py", line 1156, in __new__
    result = cls._missing_(value)
             ^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\...\AppData\Local\Programs\Python\Python312\Lib\enum.py", line 1422, in _missing_
    raise ValueError(
ValueError: (0, None) is not a valid Intents

Class `Intents` received an invalid and unexpected value `0`, a new enum item will be created to represent this value. Please update interactions.py or report this issue on GitHub - https://github.com/interactions-py/interactions.py/issues

[asyntx]

There's some migration issues with using Python 3.12.x, I suggest working with 3.11.x for now. I have also found problems on my end using the newer version

[asyntx]

Reproduced on 3.12.3, elevating issue

[AstreaTSS]

Will be fixed by #1658. Use Python 3.12.2 or a 3.11 version in the meantime.

[AstreaTSS]

Fixed by #1659.

[Suhaybu]

The temporary workaround I am using for now is switching back to Python 3.11

[AstreaTSS]

This seems to be an issue with 3.12.3 specifically. We're looking into it.