Closed lil-blue-curve closed 3 days ago
Thanks, this seems to be related to https://github.com/pandas-dev/pandas/issues/57739
This issue no longer exists on the main branch as of 2a10e04a099d5f1633abcdfbb2dd9fdf09142f8d. The script returns:
0
0 NaN
This issue no longer exists on the main branch as of 2a10e04. The script returns:
0 0 NaN
I saw in one of your edits that you have numpy 1.26.4 This issue only should only occur with numpy 2.0+
I saw in one of your edits that you have numpy 1.26.4 This issue only should only occur with numpy 2.0+
I see. Sorry for the noise.
Pandas version checks
[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest version of pandas.
[X] I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
Issue Description
Result x is changed to 0.0 even when nan_to_num is called with copy=True.
This issue is originally reported to numpy here. Looks like pandas ignores
copy=True
NumPy passes?Expected Behavior
x should not be changed when copy=True.
Installed Versions