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

[Cheaterman]

python-for-android/pythonforandroid/recipes/zope_interface/__init__.py

Line 22 in 10c5292

# this is solved in the future an error will be triggered

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.

[AndreMiras]

Thanks for the report.
I would say if it doesn't even build and fail at patching with zope interface, I don't see why not removing it indeed.
In the worst case it fails runtime, but it's still some steps further.
So yeah feel free to come up with a pull request