From: "Bird, Tim" <Tim.Bird@sony.com>
To: Jonathan Corbet <corbet@lwn.net>,
"tbird20d@gmail.com" <tbird20d@gmail.com>
Cc: "mchehab@kernel.org" <mchehab@kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] scripts/sphinx-pre-install: add '-p python3' to virtualenv
Date: Tue, 3 Mar 2020 17:07:48 +0000 [thread overview]
Message-ID: <MWHPR13MB0895EFDA9EBF7740875E661CFDE40@MWHPR13MB0895.namprd13.prod.outlook.com> (raw)
In-Reply-To: <20200302130911.05a7e465@lwn.net>
> -----Original Message-----
> From: Jonathan Corbet <corbet@lwn.net>
>
> On Mon, 24 Feb 2020 18:34:41 -0700
> tbird20d@gmail.com wrote:
>
> > With Ubuntu 16.04 (and presumably Debian distros of the same age),
> > the instructions for setting up a python virtual environment should
> > do so with the python 3 interpreter. On these older distros, the
> > default python (and virtualenv command) might be python2 based.
> >
> > Some of the packages that sphinx relies on are now only available
> > for python3. If you don't specify the python3 interpreter for
> > the virtualenv, you get errors when doing the pip installs for
> > various packages
> >
> > Fix this by adding '-p python3' to the virtualenv recommendation
> > line.
> >
> > Signed-off-by: Tim Bird <tim.bird@sony.com>
>
> I've applied this, even though it feels a bit fragile to me. But Python
> stuff can be a bit that way, sometimes, I guess.
I agree it seems a bit wonky.
The less fragile approach would have been to just
always add the '-p python3' option to the virtualenv setup hint,
but Mauro seemed to want something more fine-tuned.
As far as the string parsing goes, I think that the format of strings
returned by lsb-release (and the predecesors that sphinx_pre_install
checks) is unlikely to change.
Thanks for applying it.
-- Tim
next prev parent reply other threads:[~2020-03-03 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 1:34 [PATCH] scripts/sphinx-pre-install: add '-p python3' to virtualenv tbird20d
2020-03-02 20:09 ` Jonathan Corbet
2020-03-03 17:07 ` Bird, Tim [this message]
2020-03-03 20:01 ` Jonathan Corbet
2020-03-04 17:25 ` Bird, Tim
2020-03-04 19:53 ` Mauro Carvalho Chehab
2020-03-04 5:42 ` Mauro Carvalho Chehab
2020-03-04 6:20 ` Markus Heiser
2020-03-04 8:31 ` Mauro Carvalho Chehab
2020-03-04 9:20 ` Markus Heiser
2020-03-05 21:34 ` Mauro Carvalho Chehab
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=MWHPR13MB0895EFDA9EBF7740875E661CFDE40@MWHPR13MB0895.namprd13.prod.outlook.com \
--to=tim.bird@sony.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tbird20d@gmail.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).