-
-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API/BUG: infer_dtype_from_scalar with non-nano #52212
Conversation
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. |
@MarcoGorelli thoughts on if/how this is worth pursuing? |
sorry, missed this. I'd have thought this was fine as a bug fix - I'm at jupytercon next week though so may be a bit slow to review, but will take a look when I get a chance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice! just got some minor comments
mark = pytest.mark.xfail( | ||
reason="Construction from dict goes through " | ||
"maybe_convert_objects which casts to nano" | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this risks staying here forever, could you add strict=True
please, so that when it's fixed we remember to remove this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is strict=True no longer the default? if so, will update. (also if so: yikes)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nvm, ignore me, it's configured to be the default
Line 441 in 7304396
xfail_strict = true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me, I think it'd be OK to get this into 2.1 as it'd be a bug fix
do you want to add a whatsnew note?
🤔 not sure if this might be related
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
@mroeschke any comments, or good to go?
Thanks @jbrockmendel |
* API/BUG: infer_dtype_from_scalar with non-nano * update test * xfail on 32bit * fix xfail condition * whatsnew * xfail on windows
* API/BUG: infer_dtype_from_scalar with non-nano * update test * xfail on 32bit * fix xfail condition * whatsnew * xfail on windows
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.Needs whatsnew and targeted tests, opening to see if there are opinions about doing this as a bugfix or waiting to do it as an API change in 3.0