Blog post announcing EOL for Python 3.9

[cgoldberg]

User description

Description

Blog post announcing removal of support for Python 3.9.

Note: This was discussed in the #selenium-tlc Slack channel, but no decision was made if we should announce this or not. Feel free to close this PR if it's not necessary to make an announcement.

Motivation and Context

This post is to notify users of the upcoming removal of Python 3.9 and to state our Python version support policy.

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

---

PR Type

Documentation

---

Description

• Announce end of Python 3.9 support in Selenium 4.37

• Establish Python version support policy documentation

• Require Python 3.10+ for future selenium package installations

---

Diagram Walkthrough

flowchart LR
  A["Python 3.9 Support"] -- "EOL in v4.37" --> B["Python 3.10+ Required"]
  B --> C["Updated Support Policy"]

Loading

File Walkthrough

	Relevant files
Documentation	python3.9-eol.md Add Python 3.9 end-of-life announcement blog post                website_and_docs/content/blog/2025/python3.9-eol.md Create new blog post announcing Python 3.9 EOL Document requirement for Python 3.10+ starting with Selenium 4.37 Reference Python Developer's Guide for version support policy +14/-0

---

[netlify]

👷 Deploy request for selenium-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	3488878

[qodo-merge-pro]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	No custom compliance provided Follow the guide to enable custom compliance check.
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	✅ Remove irrelevant blog post tags Suggestion Impact: The commit updated the tags field by removing 'chrome' and 'telemetry', leaving only 'selenium' and 'python' as suggested. code diff: -tags: ["selenium", "python", "chrome", "telemetry"] +tags: ["selenium", "python"] Remove the irrelevant chrome and telemetry tags from the blog post's metadata, as the content is a general announcement about Python version support. website_and_docs/content/blog/2025/python3.9-eol.md [5] -tags: ["selenium", "python", "chrome", "telemetry"] +tags: ["selenium", "python"] [Suggestion processed] Suggestion importance[1-10]: 4 __ Why: The suggestion correctly identifies that the chrome and telemetry tags are irrelevant to the blog post's content, improving metadata accuracy.	Low
Update

[pallavigitwork]

this PR looks fine to me. TLC member with final approval can check and accept/merge.