From: "J. Bruce Fields" <bfields@fieldses.org>
To: Patrick Goetz <pgoetz@math.utexas.edu>
Cc: "Jianhong.Yin" <yin-jianhong@163.com>,
bfields@redhat.com, linux-nfs@vger.kernel.org,
Jianhong Yin <jiyin@redhat.com>
Subject: Re: [PATCH 1/2] [pynfs] remove redundant ply, gssapi and rpcgen.py modules
Date: Tue, 27 Mar 2018 15:32:36 -0400 [thread overview]
Message-ID: <20180327193236.GB22077@fieldses.org> (raw)
In-Reply-To: <fc72ad79-c558-f6bb-fa96-870ba522a427@math.utexas.edu>
On Tue, Mar 27, 2018 at 02:24:00PM -0500, Patrick Goetz wrote:
> On 03/27/2018 01:37 PM, J. Bruce Fields wrote:
> >I've never used pip. Googling around, I see some people warn about
> >potential conflicts between pip and rpm/dpkg. Would it be better to
> >recommend pip install --user?
>
> Pip is just the python package installer, similar to
> install.packages() in R or cpan in perl.
>
> The issue with rpm/dpkg/pacman is that the distribution package
> manager won't know about anything that you've installed using pip,
> which could mean, for example, that you've met a library dependency
> using pip, but apt or yum insist that the library is missing and
> needs to be installed.
Any reason not to change the README to recommend
pip install --user ply gssapi
? Seems like the safer default.
Actually now that I look my Fedora 27 laptop has both python-gssapi and
python-ply packages, so maybe there's no need for pip.
--b.
next prev parent reply other threads:[~2018-03-27 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180327172709.13071-1-yin-jianhong@163.com>
2018-03-27 17:27 ` [PATCH 2/2] [pynfs] fix nfs4.1/use_local.py && add symlink nfs4.0/use_local.py Jianhong.Yin
2018-03-27 18:37 ` [PATCH 1/2] [pynfs] remove redundant ply, gssapi and rpcgen.py modules J. Bruce Fields
2018-03-27 19:24 ` Patrick Goetz
2018-03-27 19:32 ` J. Bruce Fields [this message]
2018-03-27 19:41 ` Patrick Goetz
2018-03-27 23:14 ` Jianhong Yin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180327193236.GB22077@fieldses.org \
--to=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=jiyin@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pgoetz@math.utexas.edu \
--cc=yin-jianhong@163.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).