enhancement: Added 'errors=coerce' option in astype() #49042
Conversation
|
Going to close for now pending the discussion in the original issue. Happy to have your thoughts in that issue if you are in support of this feature. |
|
Why didn't we moved this PR ? Since it does not have a huge enhancement in the astype method. I would like to add this enhancement feature into astype (). Which help us to solve the issue. I hope! |
|
We would still be open to this enhancement given more support and discussion in #48781 first. |
|
Actually to stimulate discussion, I'll reopen this PR, sorry. |
| @@ -0,0 +1,58 @@ | |||
| .. _whatsnew_161: | |||
There was a problem hiding this comment.
if accepted, this would go in the 1.6.0 file
| @@ -302,6 +303,8 @@ def astype_array_safe( | |||
| # trying to convert to float | |||
| if errors == "ignore": | |||
| new_values = values | |||
| elif errors == "coerce": | |||
| new_values = values | |||
There was a problem hiding this comment.
how is this different from errors="ignore"?
|
This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this. |
|
Thanks for the pull request, but it appears to have gone stale. Additionally this issue could use more discussion on the original issue before moving forward to closing to await resolution on the main issue |
doc/source/whatsnew/v1.6.1.rstfile if fixing a bug or adding a new feature.