Can/should we get rid of zope_interface's fix-init patch ?

https://github.com/kivy/python-for-android/blob/10c529261d1cb19f1873bcf31db4e3f88c099488/pythonforandroid/recipes/zope_interface/__init__.py#L22

If you check on Kivy Discord (or even in buildozer issues: kivy/buildozer#1601), there's a few mentions (including mine) of twisted failing to build because of `zope_interface`. It seems to work properly if we remove the fix-init patch, so maybe we're indeed in the future (cf comment in the recipe) and this errors out?

I opened this issue (instead of directly making a PR) to discuss the situation, in particular to check if people manage to properly build projects that use twisted without issues, in which case maybe the fix-init patch isn't the root cause.

Start with pythonforandroid/recipes/zope_interface/__init__.py at the linked fix-init patch and review the related Buildozer issue kivy/buildozer#1601. Reproduce a Twisted build with and without the patch, then determine whether the patch is the cause and document the evidence needed to decide its removal.

Written by the indexing model from the issue text.