GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — fix(bigquery): allow python-dateutil 3.x and 4.x by Shriraj1901 · Pull Request #19020 · googleapis/google-cloud-python

Conversation

@Shriraj1901

@Shriraj1901 Shriraj1901 commented Nov 9, 2026

Copy link
Copy Markdown

google-cloud-bigquery only uses dateutil.relativedelta (for INTERVAL values), and the unit tests pass unchanged on python-dateutil 3.0.0 and 4.0.0, so the "< 3.0.0" cap just makes pip refuse to install it next to a newer dateutil. Raise the cap to "< 5.0.0".

Fixes #18806
Fixes #18948

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
gemini-code-assist[bot] reacted with eyes emoji
All reactions
  • 👀 1 reaction
@Shriraj1901
fix(bigquery): allow python-dateutil 3.x and 4.x
8b463fb 
google-cloud-bigquery only uses dateutil.relativedelta (for INTERVAL
values), and the unit tests pass unchanged on python-dateutil 3.0.0 and
4.0.0, so the "< 3.0.0" cap just makes pip refuse to install it next to
a newer dateutil. Raise the cap to "< 5.0.0".

Fixes googleapis#18806
Fixes googleapis#18948
@Shriraj1901
Shriraj1901 requested review from a team as code owners November 9, 2026 03:21
@Shriraj1901
Shriraj1901 requested review from sycai and removed request for a team November 9, 2026 03:21
gemini-code-assist[bot]
gemini-code-assist Bot reviewed Nov 9, 2026
View reviewed changes

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the dependency requirements in pyproject.toml for google-cloud-bigquery by increasing the upper bound of python-dateutil from < 3.0.0 to < 5.0.0. There are no review comments to address, and I have no additional feedback to provide.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
Su-001
Su-001 reviewed Nov 10, 2026
View reviewed changes
Comment thread packages/google-cloud-bigquery/pyproject.toml
"google-resumable-media >= 2.0.0, < 3.0.0",
"packaging >= 24.2.0",
"python-dateutil >= 2.8.2, < 3.0.0",
"python-dateutil >= 2.8.2, < 5.0.0",

@Su-001 Su-001 Nov 10, 2026

Copy link
Copy Markdown

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change fixes the install error, but it causes a new problem on Python 3.10.

On Python 3.10, installing google-cloud-bigquery[pandas] from this branch gives pandas 2.3.3 and python-dateutil 3.0.0. These two versions don't work together. Timezones that come from dateutil crash:

import pandas as pd
pd.Timestamp("2024-07-01 12:00", tz="dateutil/America/New_York")
# AttributeError: 'NoneType' object has no attribute 'total_seconds'

The same code works with python-dateutil 2.9.0.post0, which is what users get today.

The reason seems to be that dateutil 3.0 changed how its timezone class works, and pandas only handles this from version 3.1.1. With dateutil 4.0.0, I tried pandas 1.5.3, 2.0.3, 2.2.3, 2.3.3, 3.0.0, 3.0.1, 3.0.2 and 3.1.0, and all of them crash. pandas 3.1.1 works, but it isn't available on Python 3.10.

BigQuery's own code only uses relativedelta, so it is fine. The old < 3.0.0 limit was also protecting pandas users from this crash.

Suggested fix: keep the old limit on Python 3.10 only.

Suggested change
"python-dateutil >= 2.8.2, < 5.0.0",
"python-dateutil >= 2.8.2, < 3.0.0; python_version < '3.11'",
"python-dateutil >= 2.8.2, < 5.0.0; python_version >= '3.11'",

I tested this. Python 3.10 installs dateutil 2.9.0.post0 and the crash is gone. dateutil 3.0.0 and 4.0.0 still install on Python 3.11 and later, so both linked issues are still fixed.

If BigQuery is about to drop Python 3.10 (as #19015 did elsewhere in this repo), the 3.10 line won't be needed for long.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@Su-001

Su-001 commented Nov 10, 2026

Copy link
Copy Markdown

Thanks for working on this! I tested it locally.

What works

  • I reproduced both linked issues on main. With this PR, python-dateutil 3.0.0 and 4.0.0 install without the conflict.
  • Unit tests give the same results on dateutil 2.9.0.post0, 3.0.0 and 4.0.0:
Setup (on Windows) Passed Failed
Python 3.13, no extras 2,481 0
Python 3.13, with pandas 3.1.1 and pyarrow 2,841 4
Python 3.10, with pandas 2.3.3 and pyarrow (dateutil 2.9.0.post0 and 3.0.0 only) 2,732 2

The few failures also happen on dateutil 2.9.0.post0, so this PR doesn't cause them. They look like Windows line-ending and file-path differences.

What needs a change
Please see my comment on pyproject.toml. On Python 3.10, a normal [pandas] install now gets a pandas and dateutil pair that crashes on dateutil timezones.

The unit tests still pass with that pair, so they don't catch this. CI probably won't either, because Python 3.10 is pinned to dateutil 2.8.2, and Python 3.11+ will get pandas 3.1.1, which works.

Also worth noting
Even with the suggested fix, someone on Python 3.11+ who pins an older pandas (for example pandas==2.3.3) can still get this crash. A release note may help.

Small thing
The PR description still has the unfilled template text, including Fixes #<issue_number_goes_here>. Could you remove it?
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@parthea parthea added kokoro:force-run Add this label to force Kokoro to re-run the tests. kokoro:run Add this label to force Kokoro to re-run the tests. labels Nov 11, 2026
@yoshi-kokoro yoshi-kokoro removed kokoro:run Add this label to force Kokoro to re-run the tests. kokoro:force-run Add this label to force Kokoro to re-run the tests. labels Nov 11, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sycai sycai Awaiting requested review from sycai sycai is a code owner automatically assigned from googleapis/bigquery-dataframe-team
2 more reviewers
@Su-001 Su-001 Su-001 left review comments
@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments
Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

google-cloud-bigquery: support python-dateutil 4.x google-cloud-bigquery: python-dateutil <3.0.0 constraint blocks upgrade to 3.0.0

Uh oh!

There was an error while loading. Please reload this page.

4 participants

@Shriraj1901 @Su-001 @parthea @yoshi-kokoro
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.