Fix verbose console formatting for some types

[alexmojaki]

import datetime
import decimal
from enum import Enum, IntEnum, StrEnum

import logfire


class MyEnum(StrEnum):
    foo = 'foo'


class MyEnum2(IntEnum):
    foo = 3


class MyEnum3(Enum):
    foo = 3


logfire.configure(console=logfire.ConsoleOptions(verbose=True))


logfire.info(
    'hi',
    d=datetime.datetime.now(),
    v=decimal.Decimal('1.0'),
)
logfire.info(
    'hi',
    e1=MyEnum.foo,
    e2=MyEnum2.foo,
    e3=MyEnum3.foo,
)

Output:

11:07:08.675 hi
             │ scratch_1499.py:23 info
             │ d=2025-05-14T13:07:08.652694
             │ v=1.0
11:07:08.675 hi
             │ scratch_1499.py:24 info
             │ e1=<MyEnum.foo: 'foo'>
             │ e2=MyEnum2(<MyEnum2.foo: 3>)
             │ e3=MyEnum3(3)

All the values should look like reprs. The enums are an inconsistent mess.

Following up on #1063

Previously these raised errors or did other nonsense, that was fixed in #1071 and #1072

[sbhrwlr]

Hey @alexmojaki Can you explain the reasoning behind how enum values are represented in the logs?

For example:

1. e1: StrEnum → <MyEnum.foo: 'foo'>
2. e2: IntEnum → MyEnum2(<MyEnum2.foo: 3>)
3. e3: Enum → MyEnum3(3)

Is there a specific reason for these different formats instead of using a consistent repr like <EnumName.member: value> for all enum types?

[alexmojaki]

It's a bug. I think MyEnum3(3) is the only one looking the way it should.

[sbhrwlr]

@alexmojaki I have raised a PR to address this: PR