<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 10 November 2015 at 15:25, Alexander Kanavin <span dir="ltr"><<a href="mailto:alexander.kanavin@linux.intel.com" target="_blank">alexander.kanavin@linux.intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 11/10/2015 03:13 PM, Jussi Kukkonen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Are the pygtk changes directly related to the introspection changes? If<br>
not then maybe they should happen in another patch set.<br>
</blockquote>
<br></span>
They are; pygtk requires an old (2.x) non-introspection based version of pygobject, and the introspection patchset updates pygobject to latest 3.x release which is a much thinner layer on top of libgirepository and is incompatible with pygtk.<br></blockquote><div><br></div><div>Oh I see that now: It's patch 23 in the series for anyone else looking. I think this should be pointed out more visibly: the patchset essentially removes gtk2 python support, a feature we've had so far.</div><div><br></div><div>Maintaining python-gobject-2 and python-gtk-2 should be possible alongside the GI-based versions, but A) it only makes sense if there's real demand and B) it obviously doesn't have to happen in oe-core.</div><div><br></div><div>Jussi</div><div><br></div></div></div></div>