On Jun 18, 2015, at 03:09 PM, Didier Roche wrote: >I disagree that this patch should be dropped. Look at the upstream bug >and people thanking about that change, look at the g+ post and >developers finding sanity in installing things locally.
Sure, but I'm also getting bombarded by comments from people who don't like the change. The problem is that Ubuntu is different than upstream *and* every other distro, so this breaks folks expectations too. I don't think the change is a clear win when it's only in Ubuntu. >I agree that it would be best to follow upstream rules, but seeing that >this has been requested quite some time ago and don't see a real >solution moving upstream, I have few hopes of this getting on time for >wily. Do you have more information than the slow progress in upstream >bug report? I talk to upstream about it fairly regularly. They want to make this change too, but they have higher priority things they need to fix first. I think the best course of action would be to engage with upstream, submit a pull request, and work with them to refine the patch so that it can land upstream. I'm perfectly happy quilt patching our versions with an upstream accepted (and landed) diff until they release a version with the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460203 Title: Drop set_user_default.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1460203/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
