UnicodeDecodeError during data transmission in beep.py

[Joshua Walsky <jwalsky@…>]

Our build master was getting a Unicode Decode Error? while trying to send the build package tar file to the slave. The exception originated from line 754 of bitten/util/beep.py but was intermittent and occurred only about 20% of the time. I couldn't really determine a discenable pattern as to what would cause the exception.

I have attached a patch for beep.py which seems to have fixed this error and has been working for the past month or so in our environment. The patch is simple and performs explicit ascii encoding on the existing ret_buf data prior to concatenating with the data read from the file.

I originally saw the error under the following configuration:

• Bitten 0.5.3
• Windows 2003 Server
• Subversion 1.4
• TRAC 0.10
• Python 2.4

I started seeing this error after upgrading to TRAC 0.10 (from 0.9), Python 2.4 (from 2.3) and Bitten 0.5.3 (from 0.5).

This seems to be the same error posted by Don Fike to the Source Forge discussion list.

​http://sourceforge.net/mailarchive/message.php?msg_id=36928551 (not sure how long this link will work)

 >>
 >>File "build/bdist.linux-i686/egg/bitten/util/beep.py", line 754, in read
 >>UnicodeDecodeError: 'ascii' codec can't decode byte 0xe3 in position 10: 
 >>ordinal not in range(128)
 >>    
 >>
 >
 >Not sure, never got it in bitten, but I have been seeing it in my trac.
 >I'm guessing that it's some sort of utf encoding that doesn't sit well
 >with trac. I'm using 0.9.6 stable at the moment, and I'm hoping that
 >the release of 0.10.0 stable (any day now) will fix this issue.
 >
 >R
 >/L
 >

[osimons]

The beep.py file is gone in 0.6dev, but Unicode and encoding remains an issue. That is the topic of #119, so I'm closing this as a duplicate.