setuptools-34.0 fails with 'ImportError: No module named packaging.version'
See original GitHub issueUpgrading to setuptools-34.0 fails with ImportError: No module named packaging.version:
pip --version
pip 1.4.1 from /usr/lib/python2.6/site-packages (python 2.6)
---- Begin output of /usr/bin/pip install --upgrade setuptools ----
STDOUT: Downloading/unpacking setuptools from https://pypi.python.org/packages/4f/5d/77ab299135d7a882fff2970b45c6a77d7d79db0363c395081770632e6f1d/setuptools-34.0.0.zip#md5=927ea526582deefbf98779b2c302dd3d
Running setup.py egg_info for package setuptools
Traceback (most recent call last):
File "<string>", line 3, in <module>
File "setuptools/__init__.py", line 12, in <module>
import setuptools.version
File "setuptools/version.py", line 1, in <module>
import pkg_resources
File "pkg_resources/__init__.py", line 70, in <module>
import packaging.version
ImportError: No module named packaging.version
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "<string>", line 3, in <module>
File "setuptools/__init__.py", line 12, in <module>
import setuptools.version
File "setuptools/version.py", line 1, in <module>
import pkg_resources
File "pkg_resources/__init__.py", line 70, in <module>
import packaging.version
ImportError: No module named packaging.version
CentOS 6 in AWS.
Issue Analytics
- State:
- Created 7 years ago
- Comments:38 (6 by maintainers)
Top Results From Across the Web
ImportError: No module named packaging.version
I encountered this error on macOS after upgrading to High Sierra and re-installing MacPorts. Nothing worked until I tried this. – John Laudun....
Read more >Setuptools 34 has been released and breaks with older versions of ...
ImportError : No module named appdirs. and ImportError: No module named packaging.version. Upgrading pip as part of the CI job appears to have...
Read more >no module named packaging.version - pip - Ask Ubuntu
I solved the above problem by installing pip by the following command python -m pip install -U pip. Now pip is working fine.....
Read more >from packaging import version as pack_version ImportError
Dears, I am running a python code that generates for me this error : from packaging import version as pack_version ImportError: No module...
Read more >Bug #1658844 “most recent version does not install /usr/local ...
The failure to install the subdirs caused "ImportError: No module named packaging.version" To correct copied missing subdirs from an install ...
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 FreeTop 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
Top GitHub Comments
@rampageservices referenced method worked for me, for a clean debian-8 (jessie) install in a Vagrant VM. For those like me at python2.7:
It was the only one of all suggestions I could find that actually did the job. Thanks!
I’m unable to pip anything now because of this error. It occurred when I updated my Ubuntu trusty: Not
pip --version
And of course not pip install:
easy_install doesn’t work either with the same error. what should I do?