Drop Python 3.10?
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 25
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Python 3.10 support has become unsustainable in the current dask and distributed CI. Because so many packages no longer support it as of the latest version, conda environment resolution now takes in excess of 30 minutes, and any changes to the environment file end up with CI hanging completely.
I can see two ways out (one does not exclude the other):
- Drop Python 3.10. Please speak up here if dropping Python 3.10 would affect you.
- Migrate to a lockfile-based package manager. Personally, I've been aggressively using pixi for the last year and I'm in love with it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the current dask and distributed CI environment setup and the Python 3.10 compatibility constraints; done is an agreed decision on dropping Python 3.10, migrating to a lockfile-based package manager, or both.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100