On Sat, Jan 9, 2016 at 8:58 PM, Matthew Brett <matthew.br...@gmail.com> wrote: > On Sat, Jan 9, 2016 at 8:49 PM, Nathaniel Smith <n...@pobox.com> wrote: >> On Jan 9, 2016 10:09, "Matthew Brett" <matthew.br...@gmail.com> wrote: >>> >>> Hi Sandro, >>> >>> On Sat, Jan 9, 2016 at 4:44 AM, Sandro Tosi <mo...@debian.org> wrote: >>> >> I wrote a page on using pip with Debian / Ubuntu here : >>> >> https://matthew-brett.github.io/pydagogue/installing_on_debian.html >>> > >>> > Speaking with my numpy debian maintainer hat on, I would really >>> > appreciate if you dont suggest to use pip to install packages in >>> > Debian, or at least not as the only solution. >>> >>> I'm very happy to accept alternative suggestions or PRs. >>> >>> I know what you mean, but I can't yet see how to write a page that >>> would be good for explaining the benefits / tradeoffs of using deb >>> packages vs mainly or only pip packages vs a mix of the two. Do you >>> have any thoughts? >> >> Why not replace all the "sudo pip" calls with "pip --user"? The trade offs >> between Debian-installed packages versus pip --user installed packages are >> subtle, and both are good options. Personal I'd generally recommend anyone >> actively developing python code to skip straight to pip for most things, >> since you'll eventually end up there anyway, but this is definitely >> debatable and situation dependent. On the other hand, "sudo pip" >> specifically is something I'd never recommend, and indeed has the potential >> to totally break your system. > > Sure, but I don't think the page is suggesting doing ``sudo pip`` for > anything other than upgrading pip and virtualenv(wrapper) - and I > don't think that is likely to break the system.
It could... a quick glance suggests that currently installing virtualenvwrapper like that will also pull in some random pypi snapshot of stevedore, which will shadow the built-in package version. And then stevedore is used by tons of different debian packages, including large parts of openstack... But more to the point, the target audience for your page is hardly equipped to perform that kind of analysis, never mind in the general case of using 'sudo pip' for arbitrary Python packages, and your very first example is one that demonstrates bad habits... So personally I'd avoid mentioning the possibility of 'sudo pip', or better yet explicitly warn against it. -n -- Nathaniel J. Smith -- http://vorpus.org _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
