Bug#935887: python3-mapproxy: Change default template_dir and fix capabilities for Python >= 3.6.7

[Bas Couwenberg]

Control: tags -1 + moreinfo
Control: tags -1 - d-i

On 2019-08-27 11:52, Marek Lukács wrote:
> MapProxy does not work on Python 3.7 installs. I figured out two 
> issues,
> one related to Debian installation (directory structure) and other to
> upstream known issue:
> 
> 1. Directory structure
> 
> Debian moves templates into /usr/share/python3-mapproxy/, but default
> template_dir variable is not changed, so Python looks for templates
> instead in /usr/lib/python3/dist-packages/mapproxy/.
> 
> How to fix:
> change default directory in
> /usr/lib/python3/dist-packages/mapproxy/config/defaults.py

What is the actual issue you experience?

Do you have custom templates?

The directories moved to /usr/share/python3-mapproxy are symlinked fro 
/usr/lib/python3/dist-packages/mapproxy:

  lrwxrwxrwx root/root         0 2019-08-06 13:00 
./usr/lib/python3/dist-packages/mapproxy/service/templates -> 
../../../../../share/python3-mapproxy/service/templates
  lrwxrwxrwx root/root         0 2019-08-06 13:00 
./usr/lib/python3/dist-packages/mapproxy/test/schemas -> 
../../../../../share/python3-mapproxy/test/schemas
  lrwxrwxrwx root/root         0 2019-08-06 13:00 
./usr/lib/python3/dist-packages/mapproxy/test/system/fixture/cache_data 
-> 
../../../../../../../share/python3-mapproxy/test/system/fixture/cache_data

As long as custom templates are installed in 
/usr/share/python3-mapproxy/service/templates they should work.

How can I reproduce your issue with with templates?

> 2. Upstream code is not compatible with Python 3.7
> 
> Tempia does not correctly parses function signature with recent Python
> versions. Likely introduced with changes in Python tokenizer package
> with 3.6.7. Use keyword args as workaround.
> 
> This is already known bug in upstream:
> https://github.com/mapproxy/mapproxy/commit/81c84d47bbc77da324c36ca718fbca7dde1c1c66
> 
> How to fix:
> Patch according to commit
> https://github.com/mapproxy/mapproxy/commit/81c84d47bbc77da324c36ca718fbca7dde1c1c66

We can cherry-pick this commit and include it as a patch, as a new 
mapproxy releases will likely take some time.

How can I reproduce the issue you experience with Python 3.7?

Kind Regards,

Bas