Re: Libindic is broken on Python 2 now, should we fix or officially drop?

[Akshay S Dinesh]

>
> If we want to support 2.x we have to move to pkutil-style namespacing. That
> preserves namespaced packages, but adds support for 2.3+
>
> But, this has to be done for *all* modules and distributions. It can't be
> partially or incrementally done.
>
> I can do this if someone gives me write access to all repos and maintainer
> access to pypi

I'm not sure if I had access original was by Santhosh but I used upload
but not sure about how I can give access to others or I just need to
transfer credential

I won't need pypi access if we are dropping support for python 2.

https://pypi.org/project/libindic-utils/ and https://pypi.org/project/libindic-soundex/ already mention that python 3 is required.

So, I'll just go ahead and document the same in other projects.

Akshay