Home Original page

Pros and cons of Python sources?

nospam.nospam.Martin Schöön martin.schoon at gmail.com
Sat Nov 25 17:00:00 EST 2017 
(Martin =?UTF-8?Q?Sch=C3=B6=C3=B6n?=)

Den 2017-11-26 skrev Cameron Simpson <cs at cskk.id.au>:
> On 25Nov2017 08:34, rusi <rustompmody at gmail.com> wrote:
>>On Saturday, November 25, 2017 at 9:45:07 PM UTC+5:30, Michael Torrie wrote:
>>> The problem with mixing repository-installed packages with pip-installed
>>> packages is that there's always a chance a Debian update will overwrite
>>> a pip package, possibly with an older version.  Or a pip-installed
>>> package might bring in a new version that's not compatible with some
>>> debian-installed package, breaking something.
>>
>>On (recent?) debian/ubuntu pip seems to use the 'user-scheme'
>>which means pip runs without sudo and installs in ~/.local/lib
>>So I dont believe literal overwriting would occur
>
> Though the point should be made that one should run pip as oneself, and try
to
> avoid doing it as the root user (including avoiding sudo). Many
UNIX/Linux/etc
> users believe "installs" should be done as root, and in this case that is
> easily avoided, with all its potential for damage to the vendor supplied
> environment.

Hmm, I seem to remember not being able to install packages with pip unless I
did sudo pip.

Follow-up question: Is there a way to find out which packages were installed
using pip and which are from Debian's repo? pip list seems to list everything.

/Martin
More information about the Python-list mailing list