On Sat, Feb 28, 2015 at 09:43:14AM -0000, Matthias Klose wrote:
> On 02/27/2015 11:44 PM, Iain Lane wrote:
> > On Fri, Feb 27, 2015 at 07:17:22PM -0000, Matthias Klose wrote:
> >> we should revert that in python3.4 as well, if we cannot fix this in
> >> pygobject
> >
> > AIUI this is only available for python 2
>
> the commit itself was done on all python branches.
I know. But if you think that fixing pygobject-2 is enough then it
follows that you don't need the revert in python3.4 too, because
pygobject-2 isn't available there.
Unless you're aware of other instances of the same kind of bug.
On Sat, Feb 28, 2015 at 09:43:14AM -0000, Matthias Klose wrote:
> On 02/27/2015 11:44 PM, Iain Lane wrote:
> > On Fri, Feb 27, 2015 at 07:17:22PM -0000, Matthias Klose wrote:
> >> we should revert that in python3.4 as well, if we cannot fix this in
> >> pygobject
> >
> > AIUI this is only available for python 2
>
> the commit itself was done on all python branches.
I know. But if you think that fixing pygobject-2 is enough then it
follows that you don't need the revert in python3.4 too, because
pygobject-2 isn't available there.
Unless you're aware of other instances of the same kind of bug.
--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]