Error with `import pip` in pip 9.0.2
See original GitHub issueSome users are now experiencing an import error when calling import pip
in a function with pip 9.0.2. Downgrading to 9.0.1 fixes the issue.
Trace: https://user-images.githubusercontent.com/2273226/37558391-5e41fc94-2a24-11e8-9fdc-5884445e829a.png
More details here: https://github.com/Miserlou/Zappa/issues/1446
Issue Analytics
- State:
- Created 6 years ago
- Reactions:35
- Comments:71 (25 by maintainers)
Top Results From Across the Web
Error after upgrading pip: cannot import name 'main'
You can resolve this issue by reinstalling pip. Use one of the following command line commands to reinstall pip:.
Read more >pip install - pip documentation v22.3.1
Local directory (which must contain a setup.py , or pip will report an error). Local file (a sdist or wheel format archive, following...
Read more >pip 0.6.2 - PyPI
For instance, if a package is being installed, pip keeps track of why that package was required. Error messages should be useful. The...
Read more >Different Ways to Upgrade PIP Latest or Specific Version
Sometimes your current user may not have access to run pip commands in that case use sudo along with the pip command. You...
Read more >How to Upgrade Python PIP - Nbshare Notebooks
You are using pip version 9.0.1, however version 19.3.1 is available. You should consider upgrading via the 'pip install --upgrade pip' command.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, this is the type of change that people could expect from a
MAJOR
version update. That would be fine.Unfortunately, this massive change came in a
PATCH
update, which is supposed to fix things, not break them. This is the exact opposite of semantic versioning. And, as a result, we are seeing massive damage across the Python ecosystem.You should revert this change ASAP in another
PATCH
update, then have the major breaking change come with theMAJOR
version update. Now that you’ve already broken everything for everybody prematurely, I think they will be more aware that the actual major change is coming.I also think it’s a cop out to say that this was documented and announced already, considering that it was not documented in the stable documentation, and that the announcement said that the break would happen for the major version, not for in a patch a month prior.
Please, just save everybody a massive headache, revert this problem and start actually adhering to semantic versioning.
Come on… making a huge breaking change in a single
x.x.PATCH
version bump? For a top level method that’s called “main”? I think that’s pretty poor form…