15372 2024-01-29 14:30:28 +0000 Mark python packages as externally managed 2026-10-28 11:51:21 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 4.3 x86 Multiple NEW Medium enhancement 6.2 1 ross.burton ross.burton meta.mr.watcher meta.watcher randy.macleod tim.orling --- --- Yes (doc changes required) oldest_to_newest 98057 0 ross.burton 2024-01-29 14:30:28 +0000 As per https://packaging.python.org/en/latest/specifications/externally-managed-environments/, we should mark /usr/lib/python3.X as "externally managed", so that pip doesn't try and delete/upgrade/install into it directly. 1) tell python and pip to look in /usr/local/ so that there is still somewhere system-level to write to 2) Drop an EXTERNALLY-MANAGED file into /usr/lib/python3.X. Regarding (1), https://github.com/pypa/distutils/pull/70 looks relevant. 98664 1 tim.orling 2024-03-28 15:18:47 +0000 I believe this means that for crops containers we will need virtualenv installed (which is already required for debian-12 anyway). Otherwise, the user cannot run `pip install --user` at runtime? 98667 2 tim.orling 2024-03-28 15:28:12 +0000 This would be possibly too invasive or affect other layers in some odd behaviour changes, so moving to 5.1 M1. 98668 3 ross.burton 2024-03-28 16:01:06 +0000 pip install --user will still work. 98673 4 tim.orling 2024-03-28 18:24:13 +0000 (In reply to Ross Burton from comment #3) > pip install --user will still work. Yeah, I think I meant `pip install` will not work without `--user`. Munging multiple things from some work happening in crops for debian-12 and virtualenv.