Skip to content

Dataframes: Permit installation of pandas v3.0#1406

Merged
amotl merged 1 commit intomainfrom
pandas3
Feb 8, 2026
Merged

Dataframes: Permit installation of pandas v3.0#1406
amotl merged 1 commit intomainfrom
pandas3

Conversation

@amotl
Copy link
Copy Markdown
Member

@amotl amotl commented Feb 8, 2026

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Feb 8, 2026

Walkthrough

This PR updates time frequency specifications from "S" to "s" in dataframe creation functions and adjusts pandas version constraints in requirement files across both Dask and Pandas implementations.

Changes

Cohort / File(s) Summary
Frequency Parameter Updates
by-dataframe/dask/insert_dask.py, by-dataframe/pandas/insert_pandas.py
Updated time frequency argument in makeTimeDataFrame from "S" (uppercase) to "s" (lowercase).
Pandas Version Constraints
by-dataframe/dask/requirements.txt, by-dataframe/pandas/requirements.txt
Tightened and broadened pandas version constraints; Dask now pins <3.1 while Pandas shifted from exact (==2.3.\*) to range (>=2.3,<3.1).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 From S to s, the seconds now flow,
Frequency whispers in lowercase glow,
Pandas versions expand with a bound,
Compatible updates all around!

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: permitting pandas v3.0 installation by updating version constraints in requirements files and code.
Description check ✅ Passed The description is related to the changeset, explaining that the PR makes examples ready for pandas 3 released on Jan 21, 2026, with relevant issue references.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch pandas3

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments
by-dataframe/dask/requirements.txt (1)

5-5: Consider adding a lower bound for pandas.

The pandas requirements file uses pandas>=2.3,<3.1, but here only an upper bound is specified. This is likely fine since dask[dataframe]>=2024.4.1 transitively constrains the pandas lower bound, but adding >=2.3 would make the constraint explicit and consistent across both example projects.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@amotl amotl marked this pull request as ready for review February 8, 2026 00:48
@amotl amotl requested review from hammerhead and surister February 8, 2026 00:49
@amotl amotl merged commit 9895214 into main Feb 8, 2026
7 checks passed
@amotl amotl deleted the pandas3 branch February 8, 2026 01:02
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.

1 participant