2 ms·
Look at the pip issue history. most recently (october?) they vendored some package that was a system dependency before, and it broke the vendored versions of p
by wokwokwok 6y ago
Look at the pip issue history.
most recently (october?) they vendored some package that was a system dependency before, and it broke the vendored versions of pip (eg. on debian).
I get, “not their fault” debian goes and modifies packages... but from a user perspective: it broke.
I would say my experience is roughly on every six months something to do with pip breaks for me... but I really cant be bothered trying to keep track of it.
I just try to avoid using it now. Down vote all you like, I don't care. Pip has broken my CI enough times its lost any good will it ever had with me.
- detaro 6y ago> and it broke the vendored versions of pip Wait, Debian updated their pip, breaking it in the process without noticing?