From: "Jason Gunthorpe" <jgg@ziepe.ca>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: [kernel.org users] Pip dependency problem with b4
Date: Mon, 23 Mar 2020 13:56:52 -0300 [thread overview]
Message-ID: <20200323165652.GA20941@ziepe.ca> (raw)
In-Reply-To: <20200323151333.samun53vkbsj7fzt@chatter.i7.local>
On Mon, Mar 23, 2020 at 11:13:33AM -0400, Konstantin Ryabitsev wrote:
> On Mon, Mar 23, 2020 at 08:03:45AM -0700, James Bottomley wrote:
> > > > jejb@amdmilan1:~/git/linux-build$ b4 --help
> > > > Traceback (most recent call last):
> > > > File "/home/jejb/.local/bin/b4", line 6, in <module>
> > > > from b4.command import cmd
> > > > File "/home/jejb/.local/lib/python2.7/site-
> > > > packages/b4/__init__.py",
> > >
> > > ^^^^^^^^^
> > > Sorry, please use python 3.
> >
> > I can fix it manually, but pip should have said ... it does for most
> > other packages.
>
> I've added python_requires='>=3.6' to the proper place, so 0.3.4 will do
> the right thing.
Unrelated, but when using pip to install b4 into a virtual env
directly from git (not via some pip cloud) it blows up as setup.py
imports b4, and b4 imports all kinds of stuff..
Jason
next prev parent reply other threads:[~2020-03-23 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 14:47 Pip dependency problem with b4 James Bottomley
2020-03-23 15:00 ` Konstantin Ryabitsev
2020-03-23 15:03 ` [kernel.org users] " James Bottomley
2020-03-23 15:13 ` Konstantin Ryabitsev
2020-03-23 16:56 ` Jason Gunthorpe [this message]
2020-03-23 17:08 ` Konstantin Ryabitsev
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=20200323165652.GA20941@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=James.Bottomley@hansenpartnership.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.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