field.widget used to be Any in version 0.19.1, so code like widget.choices worked just fine, although it wasn't typed. Now that widget has a specific type of Widget | type[Widget], all our code involving widgets is full of errors since type[Widget] doesn't have attributes on it. Is this an oversight, or is there some reason widget could be a type? If so, what's the best way to work with widgets in our code with type-checking? Right now, we're blocked from upgrading to 0.20.0 as a result.
field.widgetused to beAnyin version0.19.1, so code likewidget.choicesworked just fine, although it wasn't typed. Now that widget has a specific type ofWidget | type[Widget], all our code involving widgets is full of errors sincetype[Widget]doesn't have attributes on it. Is this an oversight, or is there some reasonwidgetcould be a type? If so, what's the best way to work with widgets in our code with type-checking? Right now, we're blocked from upgrading to0.20.0as a result.