Hi Manny (2024.05.02_19:34:03_+0000) > I’m a bit confused because “pip3 list” shows a list of 146 packages, > but not argostranslation. Why did all those other packages survive the > upgrade? I wonder if some of them are somehow managed by apt.
Yes, probably. > > So, I'm afraid you're well out of the supported area of pip. > > Sorry. > > Is it necessary for aptitude full-upgrade to withhold information from > the user about package destruction or removal? Ideally users would > get a loud warning when actions are taken that are expected to impact > an installed package. If it’s a mission critical tool, users need to > be able to back out of the upgrade and assess the consequences. Anything you install without apt, in /usr/local, /opt, etc. is outside of apt's area of responsibility. It's up to you to manage these yourself. > I would also like to mention a fifth defect I just discovered: > > ⑤ argostranslate was only /partially/ removed. > > There are some big language files that were originally installed by > argostranslate. The argostranslate executable survived the upgrade but > not some of the modules it relies on, leaving it in a broken partially > existent state with no information given to the user. The language > packs remained in tact. I don’t know where on the filesystem they > live, but when I installed argostranslate again the previous language > packs were found and automatically available for use. They're probably there, just not importable in your new python. Have a look around in /usr/local. > The pip package manager has an uninstall procedure and since pip is > the manager of the argostranslate package, users rely on it to keep > track of the objects associated to the application. Pip is a far less expansive package manager than apt. It's only responsible for installing libraries and applications *within* a particular Python install. It doesn't try to do anything beyond that. Stefano -- Stefano Rivera http://tumbleweed.org.za/
