It's not like there is a "rep" you can call at "python" if this is now breaking your build process.
edit: almost all of these replies have missed my point. Yes, you can still use python2, but if you depended on pip for your build process (which I would consider "infrastructure"), then you are out of luck for this and there is nobody you can call to fix it for you.
Yes open-source is clearly worse for giving you the right and means. Vs being subject to the whims and profitability of a company.
It doesn't matter whether it's open source or not, there has to be a line on these things, and there's been more than enough time given here.
It actually does: with open-source you are not bound to the vendor if it isn't cooperative, but can pay anyone else willing and able to do the work. Plenty consultancies will happily fix old bugs or backport fixes in open-source software for you, but can't do much about closed software you depend on.
On the other hand, you would have enjoyed a royalty-free, world-wide permission to use, distribute, and modify the code base at your will.
So I'd say, not a bad wager if you're willing to do the extra work of keeping your software up to date over time (which otherwise you'd have been paying someone to do, in case of a proprietary infrastructure).
Using python2 is acceptable for you, but using an old version of pip is not acceptable?
Damn it, Python 3 has been out for years now. There is zero excuse.