build(deps): bump matrix-client from 0.3.2 to 0.4.0 in /requirements

[dependabot[bot]]

Bumps matrix-client from 0.3.2 to 0.4.0.

Release notes

Sourced from matrix-client's releases.

v0.4.0

This is a new release to address the incompatibility between matrix-python v0.3.2 and Synapse v1.38.0+. See #320 for the full details.

Changes since v0.3.2:

• Experimental support for encrypted rooms has been implemented. Note that the functionality is disabled by default, but can be enabled by first installing the native libolm library (v3.0.0+), then the encryption-related python dependencies with:

  pip install matrix-client[e2e]
  

• Add an option (use_authorization_header) for sending auth tokens using the HTTP Authorization header instead of the access_token query parameter.

• Add the ability to set the room name and whether room federation is allowed with create_room().

• Catch MissingSchema errors that could be raised by the http library (see issue #221 for details).

• Add urllib3 as an explicit dependency.

• Include the SDK version in the User Agent of requests.

• Speed up membership handling code in rooms.

• Use lexicographical sort to room displayname calculation.

• Add a new method, whoami, for determining the Matrix ID of the currently authenticated user.

• Better support for global vs. per-room display names.

• Better handling of users who lack a display name.

• Add support for specifying a filename when uploading media.

• Numerous fixes to the tests.

Commits

• 887f5d5 Release v0.4.0
• 82fb7d7 handle smaller sync responses introduced in synapse 1.38.0 (#321)
• a469d53 Update README to point to nio as an alternative library
• 06580f7 Remove use of deprecated methods in examples
• 0b5033c Add deprecation info in a docstring
• a253134 Remove --process-dependency-links section
• 726db6a Replace calls of deprecated login methods in examples
• c091ea8 Pin dependency versions per semver
• 76a6ffc Disable e2e tests when olm can't be imported
• 53af458 Refactor CI config to eliminate tox
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[istankovic]

@fredo, @ulope, why do we have matrix-client pinned to 0.3.2? Apparently it's been like that since aa0854b4d8f62eae33abc4337964242e7675f091.

Also, matrix-client is basically unmaintained, seems to be superseded by https://github.com/poljar/matrix-nio.

[ulope]

@istankovic Because we've heavily modified it via method overrides (and in some cases where no suitable method override was possible by copying code into and then modifying it in our subclasses).

We had a project to migrate to matrix-nio a while back. It only provides a fully featured client for asyncio. For other frameworks it can be used as a "No IO" library (as the name suggests). At the time we didn't have the aio-gevent bridge yet and therefore would have had to implement the IO part on top of gevent ourselves. We stopped the porting effort since other issues were more pressing.

So in summary upgrading this will require carefully looking at the changes and tracking whether we need to modify any of our overridden / changed methods as well.

[istankovic]

@ulope: [...]

So in summary upgrading this will require carefully looking at the changes and tracking whether we need to modify any of our overridden / changed methods as well.

Right, thanks for the detailed reply!