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
{{ message }}
Repository navigation
BUG: String fields in compound dtypes don't resize as might be expected #8969
Just to note, my half plan is that we deprecate "S" mostly (which doesn't actually change much). It would still be valid input to some functions like np.array() that do honor the fact that it can represent any length; and those should be the vast majority of use cases.
For all other cases, we would then force "S0" to get the same result without any ambiguity (at least in the long run).
Activity
BUG: Disallow flexible dtypes in compound types
BUG: Disallow flexible dtypes in compound types
seberg commentedon Feb 2, 2021
Just to note, my half plan is that we deprecate
"S"mostly (which doesn't actually change much). It would still be valid input to some functions likenp.array()that do honor the fact that it can represent any length; and those should be the vast majority of use cases.For all other cases, we would then force
"S0"to get the same result without any ambiguity (at least in the long run).