[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170619074653.4fbcdd36@lwn.net>
Date: Mon, 19 Jun 2017 07:46:53 -0600
From: Jonathan Corbet <corbet@....net>
To: Christoph Hellwig <hch@...radead.org>
Cc: Mauro Carvalho Chehab <mchehab@...pensource.com>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
SeongJae Park <sj38.park@...il.com>,
Markus Heiser <markus.heiser@...marit.de>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Max Filippov <jcmvbkbc@...il.com>
Subject: Re: [PATCH] changes.rst: explain the usage of virtual environment
On Mon, 19 Jun 2017 06:08:37 -0700
Christoph Hellwig <hch@...radead.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
Powered by blists - more mailing lists