matrix-org / matrix-org/matrix-python-sdk

Remove support for python 2.7 and 3.4

Open
#262 20 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

architecture enhancement question
Dominant language
Python
Stars
266
Forks
118
PR merge metrics
No merged PRs in 30d

Description

We had a long conversation in
#matrix-python-sdk:matrix.org
a couple weeks ago about the benefit of only supporting versions of python that
support asyncio and came to the conclusion that unless there are major projects
using python 2 or 3.4 that need this sdk, it would be beneficial to the project
to move to being 3.5+ only.

I'd like it if everyone who has a project using this sdk could comment here
briefly saying whether a switch to 3.5+ only would negatively affect their
project or not. It would be great if you could comment regardless of whether it
would or would not affect you.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the discussion in issue #262 and the linked #matrix-python-sdk:matrix.org conversation; no source file or test is identified in the report. Determine whether any projects still depend on Python 2.7 or 3.4, then review the repository’s version-support configuration and compatibility references. Done means the support policy is agreed and the affected project metadata, code, and tests consistently target Python 3.5+.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.