aglinxinyuan opened a new pull request, #6270:
URL: https://github.com/apache/texera/pull/6270

   ### What changes were proposed in this PR?
   
   Python 3.10 reaches **end of life in October 2026** (already security-only 
per the [Python devguide](https://devguide.python.org/versions/)), and the 
scientific-Python ecosystem is dropping it (numpy 2.3+ requires ≥3.11, 2.5+ 
requires ≥3.12). Keeping 3.10 in the matrix forces us to cap each scientific 
dependency to its last 3.10-compatible release — most recently numpy in #6231.
   
   This drops Python 3.10 and makes **3.11** the new floor (3.11 is supported 
until Oct 2027):
   
   | File | Change |
   | ---- | ------ |
   | `.github/workflows/build.yml` | pyamber matrix 
`["3.10","3.11","3.12","3.13"]` → `["3.11","3.12","3.13"]` |
   | `amber/pyproject.toml` | Ruff `target-version` `py310` → `py311` |
   | `bin/pylsp/Dockerfile` | base image `python:3.10-slim` → 
`python:3.11-slim` |
   | `docs/contribution-guidelines/guide-for-developers.md` | drop 3.10 from 
setup instructions |
   | `docs/tutorials/guide-to-enable-llm-agent.md` | `Python 3.10+` → `Python 
3.11+` |
   
   ### Any related issues, documentation, discussions?
   
   Closes #6269. Proposed in discussion #6247. Motivating case: #6231 (numpy 
capped at 2.2.6 to stay 3.10-compatible).
   
   ### How was this PR tested?
   
   CI: the `pyamber` and `amber-integration` jobs now run on Python 
3.11/3.12/3.13. There are no source changes — the amber module already built 
and tested on 3.11, which was an existing matrix leg. Verified locally that 
`amber/requirements.txt` + `amber/operator-requirements.txt` resolve on Python 
3.11 (`uv pip compile ... --python-version 3.11` → 112 packages, no conflicts).
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 4.8 [1M context])
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to