-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
While it is nice to have a more up to date pip in our toolchain, it seems like
it caused some weirdness with user installs where their system default pip was
<10.0. (See https://stackoverflow.com/questions/49836676/error-after-upgrading-pip-cannot...)
Typical failure looks like this:
cannot import name 'main'