Skip to content

Investigate:future warning 2 #117

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

Open
drBosse opened this issue Sep 28, 2022 · 3 comments
Open

Investigate:future warning 2 #117

drBosse opened this issue Sep 28, 2022 · 3 comments

Comments

@drBosse
Copy link
Contributor

drBosse commented Sep 28, 2022

When building the following warning is issued

Investigate the consequences for verifa metrics and create issues for any needed work

verifa/metrics/routes/tempo.py:106: FutureWarning: In a future version, df.iloc[:, i] = newvals will attempt to set the values inplace instead of always setting a new array. To retain the old behavior, use either df[df.columns[i]] = newvals or, if columns are non-unique, df.isetitem(i, newvals)
self.data.loc[:, ("Date")] = pandas.to_datetime(self.data.loc[:, ("Date")], format="%Y-%m-%d")

@lolpatrol
Copy link

This issue might suffer from a lack of definition.

@drBosse drBosse changed the title future warning 2 Investigate:future warning 2 Oct 6, 2022
@kvarak
Copy link
Contributor

kvarak commented Oct 8, 2022

According to the discussion here: pandas-dev/pandas#48480 this might be a bug and fixed in the coming release of 1.5.1 (https://github.com/pandas-dev/pandas/milestone/98). Let's see when that's released if this still is a problem.

@kvarak kvarak self-assigned this Oct 28, 2022
@kvarak
Copy link
Contributor

kvarak commented Oct 28, 2022

Pandas 1.5.1 did not solve the warning.

@kvarak kvarak removed their assignment Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants