Re: [PATCH v2 3/3] gnu: Add python2-wxpython.

[Danny Milosavljevic]

Hi,

wxPython bundles wxwidgets. That's why we cd to "wxPython/wxPython" in order to 
avoid building it.

So wxPython as we build it requires wxwidgets as input.

But wxwidgets has multiple backends it supports, among them gtk. It should work 
to just leave off the gtk dependency on wxPython - since wxPython itself 
shouldn't require gtk.

The intention is that wxwidgets provides a backend-independent interface. I 
think the same should be true about wxPython. I'll check it some more.

wxPython seems to use SWIG in order to generate Python bindings to the C++ 
classes of wxwidgets.

> I checked the references of the built package like this:
> 
> $ guix gc --references $(./pre-inst-env guix build python2-wxpython)
> /gnu/store/1xfc2pwr7qfjib9kfy3n2hjq56z7jyjx-python-2.7.11
> /gnu/store/6njycb0nzbczqbzvcyn1vw5sg7xsaanr-python2-setuptools-18.3.1
> /gnu/store/9nifwk709wajpyfwa0jzaa3p6mf10vxs-gcc-4.9.3-lib
> /gnu/store/a5xcl27fflh6ppysf5wrsfnn3ly2gyhy-python2-wxpython-3.0.2.0
> /gnu/store/fdlind5y49q37m1g1wsvx840q2scrp6x-wxwidgets-gtk2-3.0.2
> /gnu/store/m9vxvhdj691bq1f85lpflvnhcvrdilih-glibc-2.23
> /gnu/store/ykzwykkvr2c80rw4l1qh3mvfdkl7jibi-bash-4.3.42
> 
> assuming that wxPython needs these packages at run-time, 

I think it doesn't.

It's easy to test it in a container which provides wxpython and python by 
writing a small test program in it.