Message2655

No, and I wouldn't have gone hunting for this at this time, but I as looking into 1661679 (Invalid
types.UnicodeType), saw it used PyString instead of PyUnicode by mistake and noticed several redundant allocations, so while submitting the 1661679 patch I also tweaked the code.

I saw the roadmap about v.Next focusing on cleanup and such, but this was low hanging fruit, already in the neighborhood and a straightforward patch so I went for it.

What, that's a bad thing?