Comment 3 for bug 1268578

15:28 < asac> pitti: is it better from your perspective to implement a workaround in unity8 for the pygi
              regression (compared to just backout pygi changes?)? whats the real fix?
15:28 < pitti> asac: if you need to fix it right now, you can add the workaround (it won't hurt after the fix)
15:29 < pitti> asac: I need to catch simon feltman about this, but he's asleep, so will need to wait until tomorrow
15:30 < asac> pitti: so just reverting the pygi isnt feasible technically? point is that unity8 would have to land
              with a workaround and unity8 is pretty big beast
15:31 < asac> we can do that, but from outside perspective i see both options as valid and would choose whatever
              is less work :)
15:31 < asac> (assuming that we solve this problem upstream anyway)
15:31 < pitti> asac: certainly it's feasible
15:32 -!- pmcgowan [~pat@91.189.91.3] has joined #ubuntu-touch
15:34 < asac> pitti: so is the change/workaround in unity8 the right thing to do? if its the right thing anyway, i
              would go the unity8 route; otherwise only if its more work than a revert upload ..
15:34 * asac still wonders how python is hitting us at all in phone
15:34 < asac> thought we dont do python there :/
15:34 < pitti> yeah, I thought that, too
15:34 < pitti> asac: currently testing a reversion of the corresponding commit in pygobject
15:35 < asac> cool