diff options
| author | Maximilian Bosch <maximilian@mbosch.me> | 2019-10-26 10:40:14 +0200 |
|---|---|---|
| committer | Maximilian Bosch <maximilian@mbosch.me> | 2019-10-26 10:58:56 +0200 |
| commit | 22470fff35a2b4de1a898175675dace9f627fdeb (patch) | |
| tree | 15b15aabb38f9da9edca2060c62eda7f2d032173 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | e478127e8006aa012cfb960503b42466329e1a9a (diff) | |
mautrix-telegram: fix build
With updating `pluggy` to `0.13.0`[1] the way how python modules are
imported during pytest changed which broke all modules that had a
`coding: future_fstrings` annotation at the top which used to be needed
for python <=3.5. This only affected the tests, deploying a
`mautrix-telegram` from master with `doCheck = false;` works fine.
I applied a patch for `mautrix-telegram` which drops python 3.5 compat
(this package is intended to be used as application with python 3.7, so this
should be fine on master/unstable) and modified `mautrix-appservice`
accordingly as a lot of things on master changed since their last
release, so applying a patch didn't work there.
Resolves #71996
[1] faf8cfba4ecd86186bb2d965f6d6386a08aba6a6
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
