On Jan 25, 7:34 pm, "Edward K. Ream" <[email protected]> wrote:
> There is a problem with g.getPythonEncodingFromString with Python 3.x > on both Windows 7 and ubuntu. I suspect it's a chicken-and-egg > problem: we are trying to guess the encoding of a file after having > read it That's exactly what it was. getPythonEncodingFromString now converts 's' *temporarily* to unicode so that it can read the encoding line. We don't care about encoding errors because if the first line is in fact an encoding line it will have only ascii characters. This fix was part of rev 2762. EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
