31 Dec
2015
31 Dec
'15
12:26 p.m.
On 19 December 2015 at 08:24, Armin Rigo <arigo@tunes.org> wrote:
On Fri, Dec 18, 2015 at 1:56 PM, Oscar Benjamin <oscar.j.benjamin@gmail.com> wrote:
It seems to have already been fixed on the py3k branch so I'm not sure if it needs reporting:
We usually look at the py3.3 branch, which is for Python 3.3 compatibility; if it's also fixed there then there is nothing more to report.
Finally found time to check this. It's fixed on py3k and py3.3 so nothing to report. -- Oscar