Skip to content

Added Test support for Python 3.15 - #6897

Draft
p-r-a-v-i-n wants to merge 1 commit into
reflex-dev:mainfrom
p-r-a-v-i-n:python315
Draft

Added Test support for Python 3.15#6897
p-r-a-v-i-n wants to merge 1 commit into
reflex-dev:mainfrom
p-r-a-v-i-n:python315

Conversation

@p-r-a-v-i-n

@p-r-a-v-i-n p-r-a-v-i-n commented Aug 17, 2026

Copy link
Copy Markdown

All Submissions:

  • Have you followed the guidelines stated in CONTRIBUTING.md file?
  • Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change

Please delete options that are not relevant.

  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

The Python 3.15 beta is out. so from source:

We strongly encourage maintainers of third-party Python projects to test with 3.15 during the beta phase and report issues found to the Python bug tracker as soon as possible. While the release is planned to be feature-complete entering the beta phase, it is possible that features may be modified or, in rare cases, removed up until the start of the release candidate phase (2026-08-04). Our goal is to have no ABI changes after beta 4 and as few code changes as possible after the first release candidate. To achieve that, it will be extremely important to get as much exposure for 3.15 as possible during the beta phase.

This includes creating pre-release wheels for 3.15, as it helps other projects to do their own testing. However, we recommend that your regular production releases wait until 3.15.0rc1, to avoid the risk of ABI breaks.

I took reference from #5859
does this make sense ?

Review in cubic

@p-r-a-v-i-n
p-r-a-v-i-n requested a review from a team as a code owner August 17, 2026 09:48
@greptile-apps

greptile-apps Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR expands CI coverage to Python 3.15 and moves both performance workflows from Python 3.14 to Python 3.15.

  • Adds Python 3.15 to unit, integration, and app-harness test matrices.
  • Runs benchmark and Lighthouse performance jobs with Python 3.15.
  • Enables prerelease selection for the benchmark job’s direct Python setup.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename Overview
.github/workflows/integration_app_harness.yml Adds Python 3.15 to both app-harness test matrices using the existing uv-based environment setup.
.github/workflows/integration_tests.yml Adds Python 3.15 coverage to the cross-platform integration-test matrix.
.github/workflows/performance.yml Moves benchmark and Lighthouse jobs to Python 3.15 and explicitly enables prereleases for the direct setup-python path.
.github/workflows/unit_tests.yml Adds Python 3.15 to the Linux and Windows unit-test matrix.

Reviews (3): Last reviewed commit: "Added Test support for Python 3.15" | Re-trigger Greptile

Comment thread .github/workflows/performance.yml Outdated

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

1 issue found across 4 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/unit_tests.yml">

<violation number="1" location=".github/workflows/unit_tests.yml:31">
P2: The `unit-tests` matrix adds "3.15", but the sibling `unit-tests-macos` matrix in the same file still only lists 3.10–3.14. Since this PR is titled "Added Test support for Python 3.15" and every other workflow already runs 3.15 on linux/windows, Python 3.15 is left untested on macos (the macos job runs on every main push). Add "3.15" to the macos matrix as well, or confirm the omission is intentional.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

matrix:
os: [ubuntu-latest, windows-latest]
python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
python-version: ["3.10", "3.11", "3.12", "3.13", "3.14", "3.15"]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P2: The unit-tests matrix adds "3.15", but the sibling unit-tests-macos matrix in the same file still only lists 3.10–3.14. Since this PR is titled "Added Test support for Python 3.15" and every other workflow already runs 3.15 on linux/windows, Python 3.15 is left untested on macos (the macos job runs on every main push). Add "3.15" to the macos matrix as well, or confirm the omission is intentional.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/unit_tests.yml, line 31:

<comment>The `unit-tests` matrix adds "3.15", but the sibling `unit-tests-macos` matrix in the same file still only lists 3.10–3.14. Since this PR is titled "Added Test support for Python 3.15" and every other workflow already runs 3.15 on linux/windows, Python 3.15 is left untested on macos (the macos job runs on every main push). Add "3.15" to the macos matrix as well, or confirm the omission is intentional.</comment>

<file context>
@@ -28,7 +28,7 @@ jobs:
       matrix:
         os: [ubuntu-latest, windows-latest]
-        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14", "3.15"]
     runs-on: ${{ matrix.os }}
 
</file context>

Comment thread .github/workflows/performance.yml Outdated
Comment thread .github/workflows/integration_app_harness.yml
Comment thread .github/workflows/performance.yml Outdated
@p-r-a-v-i-n
p-r-a-v-i-n marked this pull request as draft August 19, 2026 08:26
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