On Sat, 2009-10-03 at 00:42 -0400, Tom Lane wrote:
> As far as I can tell, PLyObject_ToDatum is invoking PLyUnicode_Str and
> then PyString_AsString, and what it gets back from the latter is
> (in C string notation) "\200\0". Possibly what this means is that
> python thinks that that is the correct LATIN2 representation of
> \u0080.
Well, \u0080 is \x80 in LATIN2, which is "\200\0" as a C string. So far
so good. But that does not equate to the Euro sign, which the build
farm result shows. So something is screwing up beyond this point.
