From: bfields@fieldses.org (J. Bruce Fields)
To: Liad Oz <loz@infinidat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Bundling pynfs as a python package
Date: Wed, 4 Jan 2023 20:33:28 -0500 [thread overview]
Message-ID: <20230105013328.GA12852@fieldses.org> (raw)
In-Reply-To: <CAEdO7htksvMy7TBSLupmYbXqWf427y5byGyuXSW=APn2ZUCKYQ@mail.gmail.com>
Sigh. So, last year I thought I'd continue pynfs maintenance on a
volunteer basis, but I don't think I'm going to after all. Is anyone
else interested?
I could just blindly merge things like this and push them out, but it'd
really be better to have someone that will actually take the time to, at
a minimum, do some testing....
--b.
On Tue, Jan 03, 2023 at 01:24:42PM +0200, Liad Oz wrote:
> In my company, we want to integrate pynfs as part of our python
> testing environment. To do this, we need a package that can be
> installed using pip. Currently, it is not possible to turn pynfs into
> a pip-installable package due to the directory structure. I have been
> working on a branch that introduces major changes that fix this issue
> https://github.com/LiadOz/pynfs/pull/1/files.
>
> With this new branch, to install the package you need to run pip
> install . in the root directory. For a local installation, run pip
> install -e . (which replaces the use_local modules). I have also
> updated the README with these changes.
>
> After installation, several scripts should be automatically added to
> the path (which is why using a virtual environment is recommended):
> nfs41server, nfs41testserver, nfs41testclient, nfs41proxy,
> showresults. I have checked these scripts and they seem to work.
>
> Please note that I have not finished making all the changes needed for
> nfs4.0. I could take the time to complete these changes if you think
> the bundle changes can be merged into master.
prev parent reply other threads:[~2023-01-05 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 11:24 Bundling pynfs as a python package Liad Oz
2023-01-05 1:33 ` J. Bruce Fields [this message]
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=20230105013328.GA12852@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=loz@infinidat.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