pip3 install cmake doesn't install latest version

15 views
Skip to first unread message

Tim

unread,
Aug 15, 2019, 4:04:09 AM8/15/19
to scikit-build
I think something was screwed up in the config for CMake 3.14 because pip3 thinks it is "not compatible with this Python". This is on Ubuntu 18.04 x86_64. It looks like maybe the difference is a change from `cp37-cp37m` to `py2`/`py3`?

$ pip3 -v -v -v install cmake
Collecting cmake
  1 location(s) to search for versions of cmake:
  Looking up "https://pypi.python.org/simple/cmake/" in the cache
  Returning cached "301 Moved Permanently" response (ignoring date and etag information)
  Looking up "https://pypi.org/simple/cmake/" in the cache
  Current age based on date: 309
  Freshness lifetime from max-age: 600
  Freshness lifetime from request max-age: 600
  The response is "fresh", returning cached response
  600 > 309
  Analyzing links from page https://pypi.org/simple/cmake/
....
  Using version 3.13.3 (newest of versions: 0.1.0, 0.2.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.7.1, 0.8.0, 0.9.0, 3.6.3, 3.6.3.post1, 3.7.2, 3.8.2, 3.9.6, 3.10.3, 3.11.0, 3.11.4, 3.11.4.post1, 3.12.0, 3.13.0, 3.13.1, 3.13.2, 3.13.2.post1, 3.13.3)
  Current age based on date: 1390
  Freshness lifetime from max-age: 365000000
  The response is "fresh", returning cached response
  365000000 > 1390
Installing collected packages: cmake

  Creating /home/timh/.local/bin
  changing mode of /home/timh/.local/bin/cmake to 755
  changing mode of /home/timh/.local/bin/cpack to 755
  changing mode of /home/timh/.local/bin/ctest to 755
Successfully installed cmake-3.13.3
Cleaning up...

Tim

unread,
Aug 15, 2019, 4:10:08 AM8/15/19
to scikit-build
I think something was screwed up in the config for CMake 3.14 because pip3 thinks it is "not compatible with this Python". This is on Ubuntu 18.04 x86_64. It looks like maybe the difference is a change from `cp37-cp37m` to `py2`/`py3`?

Ah I figured it out. Update pip:

    pip3 install -U pip

Now install cmake

    pip install --user cmake

Note that updating pip will break pip3, which seems to be "not working as intended": https://github.com/pypa/pip/issues/5599
Reply all
Reply to author
Forward
0 new messages