Fix: Allow IntEnum as ex, px arguments.

[phi-friday]

Pull Request check-list

Please make sure to review and check all of these items:

• Do tests and lints pass with this change?
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
• Is the new or changed code fully tested?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Is there an example added to the examples folder (if applicable)?
• Was the change added to CHANGES file?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

Description of change

Closes: #3593

[petyaslavova]

Hi @phi-friday, thank you for your contribution — I really appreciate your effort!

In this particular case, I have some reservations about merging it. The issue lies in the type of the property in question: the expected types are limited to int or timedelta, and IntEnum values are not included in that specification.

Since the type hint is explicit, we should avoid adding additional parsing logic to handle other types that fall outside the intended scope.

[phi-friday]

Hi @phi-friday, thank you for your contribution — I really appreciate your effort!

In this particular case, I have some reservations about merging it. The issue lies in the type of the property in question: the expected types are limited to int or timedelta, and IntEnum values are not included in that specification.

Since the type hint is explicit, we should avoid adding additional parsing logic to handle other types that fall outside the intended scope.

An instance of IntEnum is an instance of int, so there is no problem with type hint, but I understand the decision not to support subclasses of int.