@JulianEisel feedback on how you'd see best handled Brush Assets names translation in the UI would be appreciated. :)
__init__
of Blender-derived python classes was not called in a canonical way before when instantiating them, may very well has been skipped in some cases then.
Again, our handling of these…
@io7m the immediate work-around is to mute or fix your StretchTo constraints (to be valid, they should either target another object, or have an additional bone sub-target).
I would need to dive deep in WM/BPY code to answer for sure, but I would not find this unexpected no... Remember that the handling of Blender-defined python classes (in general), and Operator ones…
The API docs will be updated tomorrow yes, and it will also be mentioned in the 4.4 release notes.
Don't think so, these are very low Python-managed related functions, API does not have much control over them
And some similar problem was also hit during BCon24 with the video processing tool, see infrastructure/conference-video-processing#3
So there is definitively something that is not going right here.
#127025 is also related to overloading
__init__
, not sure if it's related? @mont29
#127025 was reported before the changes introduced by 1dbe94c8ac... Though it might be worth re-checking…