[python-committers] Anyone having issues with svnmerge.py and 2.6 (possibly OS X problem)?
R. David Murray
rdmurray at bitdance.com
Thu Aug 13 23:15:38 CEST 2009
More information about the python-committers mailing list
Thu Aug 13 23:15:38 CEST 2009
- Previous message: [python-committers] Anyone having issues with svnmerge.py and 2.6 (possibly OS X problem)?
- Next message: [python-committers] Anyone having issues with svnmerge.py and 2.6 (possibly OS X problem)?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 13 Aug 2009 at 15:03, Jerry Seutter wrote: > On Thu, Aug 13, 2009 at 1:44 PM, Brett Cannon <brett at python.org> wrote: >> File "/Users/brett/.slash/python/lib/python2.6/encodings/mac_roman.py", >> line 12, in encode >> return codecs.charmap_encode(input,errors,encoding_table) >> UnicodeEncodeError: 'charmap' codec can't encode character u'\u0107' in >> position 191: character maps to <undefined> >> >> >> Anyone else running into this? I tried backing up svnmerge.py to r36767 >> (sometime in March; random choice) and I am still having the problem. >> >> -Brett >> > > There's an accented c (ć, unicode 0x0107) in a log message. It looks like > svn log is outputting the character and python can't handle it. Wierd, > since svn log is supposed to convert its output to the local encoding, just > like svnmerge is trying to do. > > http://svn.haxx.se/dev/archive-2002-09/0522.shtml > > Someone isn't using the right encoding, or else svn log has a bug. I might > just be restating the obvious. Hmm. Given the presence of 'mac_roman.py' in the traceback, I wonder if Issue 6202 has any relevance here? --David
- Previous message: [python-committers] Anyone having issues with svnmerge.py and 2.6 (possibly OS X problem)?
- Next message: [python-committers] Anyone having issues with svnmerge.py and 2.6 (possibly OS X problem)?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list