Comment 8 for bug 1419695

Well, the debian bug was about this, and you commented there telling to hold on as upstream/you was working on it and going to ship something. I didn't want at the time putting pressure with a firm date for ubuntu, thinking that would be shipped way in advance upstream.

I understand that the issue is complex and backward compatibility is important, I'm happy that now we went ahead of the curve and pushed something, you are more eager to tackle this issue. You probably understand well the current issues, I can tell you that developers don't and just end up breaking their system installation mixing package system installation and pip sources (because they got the permission traceback and just bindly typed "sudo").

I did introduce the change in purpose on a non LTS release, so that we can swap this solution with a better upstream one even after Feature Freeze, but before beta I guess (as it can be seen as a bug fix, supporting better and wider use-case). I'm willing to help you, as said in my previous comment, to get that issue fixed and happy to bring any help. How can we move then forward from here and work together to getting that done so that we can get something in pip trunk soonish that I'll backport to the ubuntu package then?