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.
** Also affects: thin-client-config-agent (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pycurl (Ubuntu)
Assignee: Dmitrijs Ledkovs (xnox) => Michael Terry (mterry)
** Summary changed:
- pycurl fails with TypeError: string argument expected, got 'bytes'
+ thin-client-config-agent fails in pycurl with TypeError: string argument
expected, got 'bytes'
** Changed in: thin-client-config-agent (Ubuntu)
Status: New => Confirmed
** Changed in: thin-client-config-agent (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152222
Title:
thin-client-config-agent fails in pycurl with TypeError: string
argument expected, got 'bytes'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1152222/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
