You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lazy translation strings (e.g. django.utils.translation.gettext_lazy) are proxy objects that are not real str instances, although castable via str(). Changes in 3.x stored a State/Eventname as-is and later assumed it was a real str, so a proxy broke:
the TransitionNotAllowed message (str.join requires real str elements) — statemachine/exceptions.py;
str(state) — State.__str__ returned the proxy directly, raising TypeError: __str__ returned non-string.
Fix
Coerce to strat the point of use, keeping the lazy object untouched in storage. Coercing at assignment would resolve the translation at class-definition time, defeating the purpose of i18n (translation must resolve at display time, honoring the active locale).
exceptions.py: ", ".join(str(s.name) ...) in the TransitionNotAllowed message.
state.py: __str__ returns str(self.name); the hash uses str(self.name) for robust hashability regardless of locale.
contrib/diagram/extract.py: coerce names to str once at the domain→model boundary, so every renderer (dot/mermaid/table) receives real str.
Docs
Release notes entry in docs/releases/3.2.1.md.
Note in docs/states.md that name accepts any object castable to str, resolved at display time.
✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (aff3977) to head (bfadcb8). ⚠️ Report is 1 commits behind head on develop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes#632.
Problem
Lazy translation strings (e.g.
django.utils.translation.gettext_lazy) are proxy objects that are not realstrinstances, although castable viastr(). Changes in 3.x stored aState/Eventnameas-is and later assumed it was a realstr, so a proxy broke:TransitionNotAllowedmessage (str.joinrequires realstrelements) —statemachine/exceptions.py;str(state)—State.__str__returned the proxy directly, raisingTypeError: __str__ returned non-string.Fix
Coerce to
strat the point of use, keeping the lazy object untouched in storage. Coercing at assignment would resolve the translation at class-definition time, defeating the purpose of i18n (translation must resolve at display time, honoring the active locale).exceptions.py:", ".join(str(s.name) ...)in theTransitionNotAllowedmessage.state.py:__str__returnsstr(self.name); the hash usesstr(self.name)for robust hashability regardless of locale.contrib/diagram/extract.py: coerce names tostronce at the domain→model boundary, so every renderer (dot/mermaid/table) receives realstr.Docs
docs/releases/3.2.1.md.docs/states.mdthatnameaccepts any object castable tostr, resolved at display time.