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

Make sure that all pandas versions in range >=2.0,<=2.2 are supported #3178

Closed
5 tasks
shchur opened this issue May 24, 2024 · 0 comments
Closed
5 tasks

Make sure that all pandas versions in range >=2.0,<=2.2 are supported #3178

shchur opened this issue May 24, 2024 · 0 comments
Labels
dependency This involves dependencies issues enhancement New feature or request
Milestone

Comments

@shchur
Copy link
Contributor

shchur commented May 24, 2024

Description

  • Add unit tests to ensure that all freq-related functionality works as expected
    • Seasonality inference
    • Time features
    • Lags
  • Ensure that all above features work with both pandas 2.2 and 2.1.
@shchur shchur added enhancement New feature or request dependency This involves dependencies issues labels May 24, 2024
@shchur shchur added this to the v0.15 milestone May 24, 2024
lostella pushed a commit that referenced this issue May 24, 2024
*Issue #, if available:* #3178

*Description of changes:*
- Add more tests verifying that pandas frequencies are handled correctly
(compatible with both pandas 2.1 and pandas 2.2)

By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.


**Please tag this pr with at least one of these labels to make our
release process faster:** BREAKING, new feature, bug fix, other change,
dev setup
kashif pushed a commit to kashif/gluon-ts that referenced this issue Jun 15, 2024
*Issue #, if available:* awslabs#3178

*Description of changes:*
- Add more tests verifying that pandas frequencies are handled correctly
(compatible with both pandas 2.1 and pandas 2.2)

By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.


**Please tag this pr with at least one of these labels to make our
release process faster:** BREAKING, new feature, bug fix, other change,
dev setup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency This involves dependencies issues enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants