@ftake

Can you please explain why python3-ibus was dropped? I read the changelog, but I didn't understand the "upstream will not maintain it for python 3" sentence. if so, why upstream still accept my ibus-force-python3.patch?

As we know, openSUSE is disgarding python 2.x, and that's why @qzhao dropped ibus-sunpinyin and ibus-googlepinyin from openSUSE:Factory. If ibus upstream "will not maintain it for python3", then python-ibus will be dropped soon because the engines require it have been dropped.

@qzhao actually I tested the python3-ibus in Leap 15.0, after patching "import gobject" further, it's usable. I also tested ibus-sunpinyin (because I think it's still been using by our users), it worked well with python3-ibus and python3-gobject2 without any modification since it's really a small setup program.

So I think here's the thing:

ftake and qzhao are different in view. qzhao wanted to follow our python 2.x removal progress while ftake wanted to keep python-ibus as it is.

both have troubles for now. for ftake, python-ibus will be dropped anyway. for qzhao, you didn't test if some engines are portable...

Greetings

Marguerite

Fuminobu Takeyama (ftake) - over 5 years ago

maintainer

@MargueriteSu

At the previous update, I specified a new flag --disable-python2 introduced by the upstream. Then, that flag removes what we have called python3-ibus.

Now Python application can communicate by using IBus gobject introspection without python3-ibus. So only legacy application, which is/was written in Python 2, might be using that library.

So I asked "Do we still need python3-ibus?" before submitting the previous update. ibus-sunpinyin still requires python3-ibus? Is it possible to remove that dependency by patching to ibus-sunpinyin?

---

Fuminobu Takeyama (ftake) - over 5 years ago

maintainer

Sorry, I just asked do we still need python(2)-ibus.

Fuminobu Takeyama (ftake) - over 5 years ago

maintainer

About "ibus-force-python3.patch", "--disable-python2" allow us to build ibus without python2. And the patch was not merged as it is, implemented different way.

Cliff Zhao (qzhao) - over 5 years ago

Sorry, could you please show me the discussion record of my opinion? My memory of the context was a little hazy.