Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #189443 > unrolled thread

Removing old python packages installed with pip

Back to article view | Back to linux.debian.user

Contents

  Removing old python packages installed with pip Urs Thuermann <urs@isnogud.escape.de> - 2017-12-01 15:40 +0100
    Re: Removing old python packages installed with pip Eike Lantzsch <zp6cge@gmx.net> - 2017-12-01 16:50 +0100
      Re: Removing old python packages installed with pip David Wright <deblis@lionunicorn.co.uk> - 2017-12-02 16:30 +0100
        Re: Removing old python packages installed with pip <tomas@tuxteam.de> - 2017-12-02 16:40 +0100
      Re: Removing old python packages installed with pip Urs Thuermann <urs@isnogud.escape.de> - 2017-12-06 22:40 +0100
    Re: Removing old python packages installed with pip deloptes <deloptes@gmail.com> - 2017-12-02 07:50 +0100
      Re: Removing old python packages installed with pip Urs Thuermann <urs@isnogud.escape.de> - 2017-12-06 22:50 +0100

#189443 — Removing old python packages installed with pip

On a machine running Debian stretch I have installed python3, which is
currently python3.5.  Nothing of python3.4 is present.

But in /usr/local/lib/python3.4/dist-packages/ a number of packages is
still installed.  Probably, these have been installed using pip3 when
python3.4 was current.

Now, it seems pip3 isn't able to remove packages from that old
directory.  Is it safe to just rm -r /usr/local/lib/python3.4?

urs

[toc] | [next] | [standalone]

#189446

On Friday, December 1, 2017 3:24:47 PM -03 Urs Thuermann wrote:
> On a machine running Debian stretch I have installed python3, which is
> currently python3.5.  Nothing of python3.4 is present.
> 
> But in /usr/local/lib/python3.4/dist-packages/ a number of packages is
> still installed.  Probably, these have been installed using pip3 when
> python3.4 was current.
> 
> Now, it seems pip3 isn't able to remove packages from that old
> directory.  Is it safe to just rm -r /usr/local/lib/python3.4?
> 
> urs
Hi Urs,

If those packages were installed together with the Debian system then 
deinstall with aptitude or apt remove.
If you mix two different package installers the consequence is that one does 
not know about the other and they can interfere with each other.
On Debian always install packages the "Debian way".
Don't make a Frankendebian:
https://wiki.debian.org/DontBreakDebian

Cheers
Eike

[toc] | [prev] | [next] | [standalone]

#189468

On Fri 01 Dec 2017 at 12:42:35 (-0300), Eike Lantzsch wrote:
> On Friday, December 1, 2017 3:24:47 PM -03 Urs Thuermann wrote:
> > On a machine running Debian stretch I have installed python3, which is
> > currently python3.5.  Nothing of python3.4 is present.
> > 
> > But in /usr/local/lib/python3.4/dist-packages/ a number of packages is
> > still installed.  Probably, these have been installed using pip3 when
> > python3.4 was current.
> > 
> > Now, it seems pip3 isn't able to remove packages from that old
> > directory.  Is it safe to just rm -r /usr/local/lib/python3.4?

You should preserve /usr/local/lib/python3.4/dist-packages/,
so removing just the files, and not *all* the directories, is safer.

> If those packages were installed together with the Debian system then 
> deinstall with aptitude or apt remove.

If Debian installs files (other than empty directories) under
/usr/local/, I would file a bug. That tree is for you, not Debian.

> If you mix two different package installers the consequence is that one does 
> not know about the other and they can interfere with each other.
> On Debian always install packages the "Debian way".
> Don't make a Frankendebian:
> https://wiki.debian.org/DontBreakDebian

My understanding of "Frankendebian" is a system that mixes *Debian*
versions. There have to be ways of adding other suites of software
to a Debian system and, if they're for general rather than personal
use, the /usr/local/ tree is a good way to go. Why else bother to
have /usr/local/bin in the default $PATH?

>From the reference above: "Installing software to the /usr/local will
make it available to all users, and will not interfere with the
package manager. The stow package can be useful for managing software
installed to /usr/local."

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#189469

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Dec 02, 2017 at 09:27:43AM -0600, David Wright wrote:
> On Fri 01 Dec 2017 at 12:42:35 (-0300), Eike Lantzsch wrote:

[...]

> > If you mix two different package installers the consequence is that one does 
> > not know about the other [...]

> My understanding of "Frankendebian" is a system that mixes *Debian*
> versions [...]

Agreed, I also think that Eike's cautionary note is based on a
misinterpretation of what a Frankendebian is. Debian packagers
go out of their way to work well with locally installed software
(if you look at the packaging guidelines for big package groups,
like Debian Perl, you'll see that).

That said, extra care *is* needed when installing software outside
the distribution's package manager. That is, I think, obvious.

Even with a classical Frankendebian, I've made good experiences
(typically stable + unstable). But you've to expect difficulties
(in my case it was aptitude's more advanced, and thus complex
dependency resolver maneuvering itself into a more and more
impenetrable thicket or downright giving up). Do plan in extra
care and be prepared to learn. But there's no reason to be
afraid of that, either.

Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAloiyOYACgkQBcgs9XrR2kZBbwCfVn4UleKMV2mScsQOkKhqTNCu
TvEAnjujPW6s2UwMpyjIt8A+6STU6ajD
=pY21
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#189606

Eike Lantzsch <zp6cge@gmx.net> writes:

> On Friday, December 1, 2017 3:24:47 PM -03 Urs Thuermann wrote:
> > On a machine running Debian stretch I have installed python3, which is
> > currently python3.5.  Nothing of python3.4 is present.
> > 
> > But in /usr/local/lib/python3.4/dist-packages/ a number of packages is
> > still installed.  Probably, these have been installed using pip3 when
> > python3.4 was current.
> > 
> > Now, it seems pip3 isn't able to remove packages from that old
> > directory.  Is it safe to just rm -r /usr/local/lib/python3.4?

> If those packages were installed together with the Debian system then 
> deinstall with aptitude or apt remove.

No, as I said, it was (most probably) installed using pip3 when
python3.4 was current in Debian.  Debian packagement doesn't know
about it, so cannot uninstall it.

> If you mix two different package installers the consequence is that one does 
> not know about the other and they can interfere with each other.

No, nothing is mixed.  pip installs in /usr/local, Debian packagement
installs in /usr.

But pip3 formerly installed in /usr/local/lib/python3.4 but now seems
not to know about anymore.  Now it installs in /usr/local/lib/python3.5.
Therefore, pip3 doesn't list and cannot uninstall python packages from
the older /usr/local/lib/python3.4.  Also, python3, which is 3.5
currently, seems not to search that old directory.

I am almost sure that just removing it will be fine, but I wanted to
make sure, that no file of pip3 e.g. in /var or elsewhere still refers
to /usr/local/lib/python3.4.  That's why I asked here.

> On Debian always install packages the "Debian way".

There are Python packages like theano and keras that are not in
Debian.  They can only be installed completely manually or using
pip3.  In both cases they go to /usr/local, of course.

urs

[toc] | [prev] | [next] | [standalone]

#189460

Urs Thuermann wrote:

> Now, it seems pip3 isn't able to remove packages from that old
> directory.  Is it safe to just rm -r /usr/local/lib/python3.4?

yes it is more or less safe - it depends how you let it install - perhaps
there is also something under /usr/local/bin

regards

[toc] | [prev] | [next] | [standalone]

#189607

deloptes <deloptes@gmail.com> writes:

> yes it is more or less safe - it depends how you let it install - perhaps
> there is also something under /usr/local/bin

Thanks, I'll do it then.  And yes, there are 3 binaries in
/usr/local/bin from the theano package with the same installation
date, which I will also remove.

urs

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web