Closed dand-oss closed 3 years ago
The cause is the renaming of __init__
to __post_init__
here. Both functions are supported for post-initialisation processing but the former is a historical artifact at this point. I've been thinking of removing it as no one seems to use it and it's confusing, this bug makes me think I should. Removing the two lines linked resolves it.
Fixed - will postpone removing __init__
aliasing to a later issue.