Skip to content
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

pandas-offsets stopped being hashable #958

Closed
jaheba opened this issue Jul 30, 2020 · 6 comments
Closed

pandas-offsets stopped being hashable #958

jaheba opened this issue Jul 30, 2020 · 6 comments
Labels
bug Something isn't working

Comments

@jaheba
Copy link
Contributor

jaheba commented Jul 30, 2020

In Pandas 1.1 the freq component of the time-stamps that we use have stopped being hashable, which means, they cannot be used as keys in dictionaries. We use this in different locations in our code base.

We now have two options:

  • open an issue with pandas, requesting that the old behaviour is restored
  • change our code to not make use of this feauture
@jaheba jaheba added the bug Something isn't working label Jul 30, 2020
@AaronSpieler
Copy link
Contributor

For now we should probably change the pandas requirement to <1.1.
I also ran into problems with the pandas version.

@RenaissanceEngineering
Copy link

Still an issue.

@lostella
Copy link
Contributor

lostella commented Feb 5, 2021

@PhilipMachineLearning do you have an example to reproduce the issue?

@Forecastlife
Copy link

Still an issue 4/23/2021

@jaheba
Copy link
Contributor Author

jaheba commented Apr 26, 2021

Still an issue 4/23/2021

This should be fixed now in pandas. What version are you using?

@tonyhoo
Copy link

tonyhoo commented Nov 5, 2021

Just for whoever still have the issue. 2 quick fixes:

  1. Downgrade pandas to 1.0.x
  2. Upgrade pandas to >1.3.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants