I'm not sure if this is a bug in pycurl. I see a few fixes w.r.t. python3 bytes/string handling in pycurl uploaded by mterry (see https://launchpad.net/ubuntu/+source/pycurl/+changelog ). My naïve expectation is that "over the wire" we always pass and receive Bytes, and it's our job to encode/decode that before sending/receiving. Attaching a hacking patch, which makes thin-client-config-agent work against pycurl in raring. Not sure if it will work against quantal and earlier as well. Assigning to Mterry the pycurl portion of the bug report & asking to review merge proposal as well.
I'm not sure if this is a bug in pycurl. I see a few fixes w.r.t. python3 bytes/string handling in pycurl uploaded by mterry (see https:/ /launchpad. net/ubuntu/ +source/ pycurl/ +changelog ). My naïve expectation is that "over the wire" we always pass and receive Bytes, and it's our job to encode/decode that before sending/receiving. Attaching a hacking patch, which makes thin-client- config- agent work against pycurl in raring. Not sure if it will work against quantal and earlier as well. Assigning to Mterry the pycurl portion of the bug report & asking to review merge proposal as well.