OK looks like latest repo version is quite a bit different and doesn't have the same bug.Presumably this is a revision for the next release.Some might still might want the one line fix for 3.4.2 in the meantime.