From: Jonathan Corbet <corbet@lwn.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
SeongJae Park <sj38.park@gmail.com>,
Markus Heiser <markus.heiser@darmarit.de>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [PATCH] changes.rst: explain the usage of virtual environment
Date: Mon, 19 Jun 2017 07:46:53 -0600 [thread overview]
Message-ID: <20170619074653.4fbcdd36@lwn.net> (raw)
In-Reply-To: <20170619130837.GA25524@infradead.org>
On Mon, 19 Jun 2017 06:08:37 -0700
Christoph Hellwig <hch@infradead.org> wrote:
> On Mon, Jun 19, 2017 at 08:24:10AM -0300, Mauro Carvalho Chehab wrote:
> > As the Sphinx build seems very fragile, specially for
> > PDF output, add a notice about how to use it on a virtual
> > environment.
>
> Please don't. python venv are good at one thing only, and that is
> making a mess of your python module path. Don't ever use them on a
> system that has proper package management.
Well, they are also good for running specific versions of a given package
without disrupting the setup of your system as a whole, and when even a
system with proper package management may not offer the version you need.
I guess my question with the patch is whether this text really belongs in
changes.rst, or whether it should be part of the doc-guide.
jon
next prev parent reply other threads:[~2017-06-19 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 11:24 [PATCH] changes.rst: explain the usage of virtual environment Mauro Carvalho Chehab
2017-06-19 13:08 ` Christoph Hellwig
2017-06-19 13:46 ` Jonathan Corbet [this message]
2017-06-19 14:11 ` Markus Heiser
2017-06-19 14:38 ` Mauro Carvalho Chehab
2017-06-19 15:13 ` Markus Heiser
2017-06-20 15:03 ` Markus Heiser
2017-06-19 14:21 ` 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=20170619074653.4fbcdd36@lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jcmvbkbc@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.com \
--cc=sj38.park@gmail.com \
--cc=yamada.masahiro@socionext.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