Hi Devs
I propose dropping django-dbgettext support in the CMS in 2.2, which would mean before we release 2.1 we need to put Deprecation Warnings in there, which is why I bring this up now.
Why should we do that?
- It's an 100% untested feature
- Noone I know uses it, so again, I don't know if it works
- It duplicates a feature we already handle, doubling the work for us
- I personally believe it's a bad idea anyway.
Does anyone have any good arguments against dropping it?
Jonas