`templates_suffix`: "extension prefix" rather than suffix

Changing the file extension has real disadvantages on editors as they are not recognized anymore.

There are extensions taking care of syntax highlighting.
But there are still problems with the editor configuration.

I’ve an EditorConfig so I could modify that.
But it’s annoying and not pretty.

So, wouldn’t it be better to use an “extension prefix”? (.tmpl.py instead of .py.tmpl)
Or as I saw in another issue, just processing all files. Or the more flexible, allow to define patterns to include (e.g. ["*.py", "*.html", ".env"] or regex (^\.env$)|(\.(py|html)$)).

[pawamoy]

@ppo wouldn’t .jinja.py be recognized as Python only (not Python+Jinja)? And therefore syntax highlighting could break easily?

[mazdakb]

I am creating a Django boilerplate project, similar to Cookiecutter Django but with copier. Changing the extension (to .tmpl or anything else) can also break dependabot which looks for specific files in a designated directory. Therefore I cannot keep the dependencies of the required libraries in template up to date as it’s possible with cookiecutter. I can imagine any arbitrary tool which works like dependabot might break.