Skip to content

Conversation

@whimboo
Copy link
Contributor

@whimboo whimboo commented Jan 6, 2026

Fixes #200.

@jgraham, @gsnedders and @WeizhongX please review. Thanks

Copy link
Member

@gsnedders gsnedders left a comment

Choose a reason for hiding this comment

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

This clearly needs review from someone at Chromium more than anyone else, but:

Comment on lines +14 to +15
Historically, continued Python 3.8 support was required due to downstream CI
integrations with Apple’s and Google’s infrastructure. These systems have since
Copy link
Member

Choose a reason for hiding this comment

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

WebKit hasn't had any need for Python 3.8 since we dropped support for Xcode 12 several years ago. Our own tooling hasn't support it in a while.

It's not clear to me from #200 when Mozilla stopped needing Python 3.8 support? After upgrading systems after Ubuntu 20.04 LTS reached extended security maintenance?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think we still have some older Ubuntu versions, but we've updated all the Python to at least 3.9, and that's what the build system requires. In practice I think all the CI machines might have at least 3.10, but I'm not sure about that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Comment on lines +22 to +23
- Refresh vendored dependencies that were previously constrained by
Python 3.8 compatibility.
Copy link
Member

Choose a reason for hiding this comment

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

Note with web-platform-tests/wpt#49752 unlanded we don't have a particularly easy way to do this. :'(

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I assume that this was just a comment from your side and nothing specific to update this content with?

Comment on lines +24 to +27
- Re-run CI for Dependabot pull requests to allow dependency updates to proceed.
Some dependencies may now require Python 3.10 or newer; in those cases, we
should manually update to the latest release that remains compatible with
Python 3.9.
Copy link
Member

Choose a reason for hiding this comment

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

I did question in web-platform-tests/wpt#55608 whether we should just outright disable dependabot; it's unclear to me we're gaining much except noise with our minimum version?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think that would require a new RFC, but I'd be opposed; at least some dependencies do usefully get updates.

Comment on lines +31 to +33
Python 3.9 itself reached end of life in October 2025, which means we
will encounter similar pressure to raise the minimum version again as
dependencies may already require Python 3.10 or newer. Any further
Copy link
Member

Choose a reason for hiding this comment

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

We could also change policy about how we lock dependency versions.

We've typically gone for something approximating the fewest versions (along the lines of uv pip compile's --fork-strategy fewest); we could also use split it by the required Python version (along the lines of its --fork-strategy requires-python).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I assume this is as well something not blocking this RFC?

@jcscottiii
Copy link
Contributor

@jonathan-j-lee Could you take a look?

@jcscottiii
Copy link
Contributor

From @jonathan-j-lee:

We're already on 3.11, so I'm not expecting any problems.

Copy link
Contributor

@jonathan-j-lee jonathan-j-lee left a comment

Choose a reason for hiding this comment

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

LGTM from Chromium CI

Comment on lines +14 to +15
Historically, continued Python 3.8 support was required due to downstream CI
integrations with Apple’s and Google’s infrastructure. These systems have since
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we still have some older Ubuntu versions, but we've updated all the Python to at least 3.9, and that's what the build system requires. In practice I think all the CI machines might have at least 3.10, but I'm not sure about that.

Comment on lines +24 to +27
- Re-run CI for Dependabot pull requests to allow dependency updates to proceed.
Some dependencies may now require Python 3.10 or newer; in those cases, we
should manually update to the latest release that remains compatible with
Python 3.9.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think that would require a new RFC, but I'd be opposed; at least some dependencies do usefully get updates.

@jgraham
Copy link
Contributor

jgraham commented Jan 28, 2026

web-platform-tests/wpt#57379 for the implementation.

@whimboo
Copy link
Contributor Author

whimboo commented Jan 29, 2026

@gsnedders mind checking again now that Google approved this RFC? Thanks.

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.

Update minimum supported Python to 3.9

5 participants