What about wxPython?

What about wxPython?

It should use wxpython4. I will recheck with upstream to be 100 % sure.

Is the wxPython maintainer aware of this exception request?

Is the wxPython maintainer aware of this exception request?

It seems it already supports wxPython4. So I can switch it to python2-wxpython4, not sure whether it's better for this request :)

It doesn't really matter for this request. What matters is that the maintainer of python2-wxpython4 or wxPython is on board and willing to keep the Python 2 package.

It doesn't really matter for this request. What matters is that the maintainer of python2-wxpython4 or wxPython is on board and willing to keep the Python 2 package.

I sent e-mail to Dan (wxPython main admin), waiting for reply. I am also OK to co-maintain the wxPython until Quisk upstream finishes the port. Unfortunately, the python-wxpython4 has different maintainer, so I choosed the wxPython way.

@swt2c maintains both.

But anyway, wxpython4 is now already Python 3 only, so as a temporary solution, using wxPython is probably easier.

+1 based on your OK to co-maintain wxPython

(I've edited the title to contain wxPython for clarity)

I'm OK with maintaining wxPython/python2-wxpython a little longer. I definitely want it retired in F32 though.

The quisk port is finished now, so this is no more an issue :) Please close this request (I am not sure which resolution to choose :)