You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The path forward for pip-shims is to simplify it and not support a huge legacy of prior pythons that are EOL, and pips that are so old they should no longer be used. The prior versions of pip-shims exist and forever remain as compatibility shims for those points in time. However the complexity of this code base has outlived its usefulness and we should seek to simplify it and understand better what the API compatibility differences that are actually worth maintaining.
The text was updated successfully, but these errors were encountered:
The path forward for pip-shims is to simplify it and not support a huge legacy of prior pythons that are EOL, and pips that are so old they should no longer be used. The prior versions of
pip-shims
exist and forever remain as compatibility shims for those points in time. However the complexity of this code base has outlived its usefulness and we should seek to simplify it and understand better what the API compatibility differences that are actually worth maintaining.The text was updated successfully, but these errors were encountered: