Linux NFS development
 help / color / mirror / Atom feed
From: Bruce Fields <bfields@fieldses.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: "open list:NFS, SUNRPC, AND..." <linux-nfs@vger.kernel.org>
Subject: Re: pynfs breakage
Date: Mon, 15 Feb 2021 15:17:28 -0500	[thread overview]
Message-ID: <20210215201728.GC30742@fieldses.org> (raw)
In-Reply-To: <804830ba7fdd91cbf9348050b07f9922801d20f0.camel@kernel.org>

On Mon, Feb 15, 2021 at 03:15:08PM -0500, Jeff Layton wrote:
> Hi Bruce!
> 
> The latest HEAD in pynfs doesn't run for me:
> 
> $ ./nfs4.1/testserver.py --help
> Traceback (most recent call last):
>   File "/home/jlayton/git/pynfs/nfs4.1/./testserver.py", line 38, in <module>
>     import server41tests.environment as environment
>   File "/home/jlayton/git/pynfs/nfs4.1/server41tests/environment.py", line 593
>     def write_file(sess, file, data, offset=0 stateid=stateid4(0, b''),
>                                               ^
> SyntaxError: invalid syntax
> 
> If I revert this commit, then it works:

Yeah, sorry about that, I pushed out quickly thinking I'd tested it, but
in fact it has a bunch of mistakes.  Fixing....

--b.

> 
> commit 49ae5ba83dd98936b3f5c24431a166866b70f34a (HEAD -> master, origin/master, origin/HEAD)
> Author: J. Bruce Fields <bfields@redhat.com>
> Date:   Thu Feb 11 16:22:58 2021 -0500
> 
>     nfs41: read_file and write_file helpers
>     
>     A couple simple helpers copied from 4.0.
>     
>     Signed-off-by: J. Bruce Fields <bfields@redhat.com>
> 
> 
> Cheers,
> -- 
> Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2021-02-15 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 20:15 pynfs breakage Jeff Layton
2021-02-15 20:17 ` Bruce Fields [this message]
2021-02-15 21:22   ` Bruce Fields
2021-02-15 21:23     ` Jeff Layton

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=20210215201728.GC30742@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /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