Project

General

Profile

Logged in as brainvisa
Watch Actions

Defect #18683

closed

python packaging may be broken when mixing up several installs of the same module

Added by Riviere, Denis almost 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
brainvisa-cmake
Start date:
25/07/2018
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

We have this problem for instance on Ubuntu 18.04, where numpy is installed on the system, then we have upgraded it using pip. The install copies all modules in inverse path order, and both numpy installs end up in the same directory. New files replace older ones, which seems OK. But in fact some files have changed names, and numpy happens to try loading the older names first.
A set of compiled modules, /usr/lib/python2.7/dist-packages/numpy/core/*.x86_64-linux-gnu.so are named without the .x86_64-linux-gnu extension in the newer module, but the former ones are loaded.
So we must not copy the older ones in the install.
Maybe we should completely remove directories which already exist when copying modules in the install, but I'm not sure some are not reused partly.

Actions #1

Updated by Riviere, Denis over 5 years ago

  • Status changed from New to Closed
  • Assignee set to Riviere, Denis
  • Resolution set to Fixed

fixed by selectively deleting previous installations of numpy (r83606, r83612)

Watch Actions

Also available in: Atom PDF