Thanks Christian for triaging this bug. This is my understanding:
Python 3 support is a new feature that arrived in Vivid due to timing of Debian syncs, but actually never worked. It is not a regression since it wasn't present in any previous release. The reason it never worked was an upstream bug in the VCS snapshot that Debian took, which they've since fixed in a newer release. The newer (fixed) release is packaged in Wily. The fix would be valid to backport in an SRU (https://wiki.ubuntu.com/StableReleaseUpdates#When) Since we have only one user affected so far, Vivid will be EOL in January and I expect there won't be many new Vivid users after Wily is released this month, I think that driving a fix for this in Vivid is of low importance and don't expect that anyone will get round to doing it, so I'll set the status for Vivid to Won't Fix so as not to set unrealistic expectations. If someone wants to drive this bug through to sponsorship or upload for a fix to Vivid (see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure) then feel free to change the status to Confirmed or Triaged and please go right ahead. ** Changed in: python-memcache (Ubuntu Vivid) Status: Triaged => Won't Fix ** Changed in: python-memcache (Ubuntu Vivid) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492604 Title: python3-memcached uses invalid string handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-memcache/+bug/1492604/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
