From cca6ae1dd0a365b049db5e489baedc0c2ed63719 Mon Sep 17 00:00:00 2001 From: Folarin Benjamen Pelumi <89490327+Benflow3@users.noreply.github.com> Date: Wed, 17 Jun 2026 17:36:02 +0100 Subject: [PATCH] docs: warn about identity instability of unknown status codes in docstring Update documentation to clarify behavior of synthesized ``UNKNOWN_`` members and their equality checks. --- .../src/dexpace/sdk/core/http/response/status.py | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/packages/dexpace-sdk-core/src/dexpace/sdk/core/http/response/status.py b/packages/dexpace-sdk-core/src/dexpace/sdk/core/http/response/status.py index 522eac6..682fcb0 100644 --- a/packages/dexpace-sdk-core/src/dexpace/sdk/core/http/response/status.py +++ b/packages/dexpace-sdk-core/src/dexpace/sdk/core/http/response/status.py @@ -22,6 +22,11 @@ class Status(IntEnum): classification (`is_success`, `is_redirect`, ...) and integer comparisons intact, instead of being discarded. Integers outside 100..599 (for example ``42`` or ``1000``) remain invalid and raise `ValueError`. + + .. note:: + Synthesized ``UNKNOWN_`` members are dynamically instantiated and + are not identity-stable across lookups. Always use value equality + (``==``) or band predicates rather than identity checks (``is``). """ # 1xx Informational