[Debian-med-packaging] Bug#707341: Q: Python 2 vs Python 3 and wxgtk2.8 vs wxgtk3.0

[Karsten Hilbert]

Hi all,

I am upstream for a Python application:

	http://wiki.gnumed.de

which is packaged in Debian:

	https://packages.debian.org/search?keywords=gnumed-client

and maintained:

	http://blends.debian.org/med/tasks/practice

by the Debian Med Team:

	https://www.debian.org/devel/debian-med/

GNUmed (an Electronic Medical Record System) runs under
Python 2 with wxPython 2.8 and it Depends: on python-uno.
Recently a bug was filed against GNUmed because python-uno is
likely to go away in favour of python3-uno (which is reasonable):

	https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707341

The bug suggested we port GNUmed to Python 3 "ASAP". Now, the
"P"ossible part of ASAP is the problem:

Since ATM there does not exist either a python3-wxgtk2.8 nor
a python3-wxgtk3.0 we simply CANNOT port AND have GNUmed run
under Debian ...

I have searched the web and this list's archive for hints on
how Debian plans to handle this situation - it will apply to
quite a few packages, not just GNUmed. The only reference to
a python3-wxgtk I have been able to come up with is here:

	https://packages.debian.org/sid/python/python3-serial

_From an upstream point of view it would be much preferrable to
have available a python3-wxgtk2.8 because that would not
force us to port to BOTH Python 3 AND wxPython 3 at the same
time.

What's the current Debian position ?

Thanks,
Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346