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

pct_change specifies fill_method='pad' #82

Closed
wants to merge 1 commit into from
Closed

Conversation

talumbau
Copy link
Member

  • Don't rely on default argument for fill_method as it was deprecated in Pandas 2.1.

@codecov-commenter
Copy link

codecov-commenter commented Jan 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (9da4947) 73.76% compared to head (a3a16a2) 73.76%.

❗ Current head a3a16a2 differs from pull request most recent head e03c79a. Consider uploading reports for the commit e03c79a to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #82   +/-   ##
=======================================
  Coverage   73.76%   73.76%           
=======================================
  Files          24       24           
  Lines        1616     1616           
=======================================
  Hits         1192     1192           
  Misses        424      424           
Flag Coverage Δ
unittests 73.76% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

 - Don't rely on default argument for `fill_method` as it was deprecated in Pandas 2.1.
@talumbau
Copy link
Member Author

@rickecon @jdebacker I noticed that the linting check is failing on files I didn't change. I like black as a formatter (good choice!). Do you want me to submit a PR that gets linting passing again? I saw this deprecation warning when running the example and thought it would be a good way to kick the tires. Let me know what makes sense.

@jdebacker
Copy link
Member

@talumbau I appreciate you opening another PR to fix the formatting. We use black with the 79 character line option. If you upgrade to the most recent black version and run black -l 79 ./ from the OG-USA directory, this should resolve the linting failures.

@rickecon
Copy link
Member

rickecon commented Feb 8, 2024

@talumbau. Yes. We just merged a PR into OG-Core (PR #898) that set the black requirement in environment.yml to black>=24.1.1. We found that black version 23 formatted differently. We also might need to restrict the Python version in OG-USA to be <3.12.

@rickecon
Copy link
Member

@talumbau @jdebacker. The change in this PR has been added to PR #89, along with another line in the macro_params.py module that required a similar update. I am closing this PR.

@rickecon rickecon closed this Feb 12, 2024
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

Successfully merging this pull request may close these issues.

4 participants