Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1669103
| From | Markus Heiser <markus.heiser@darmarit.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] changes.rst: explain the usage of virtual environment |
| Date | 2017-06-19 16:20 +0200 |
| Message-ID | <tU5H4-3IR-19@gated-at.bofh.it> (permalink) |
| References | <tU32y-1Yb-13@gated-at.bofh.it> <tU4Bl-33y-31@gated-at.bofh.it> <tU5e2-3jx-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> Am 19.06.2017 um 15:46 schrieb Jonathan Corbet <corbet@lwn.net>: > > 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. Hi, here are my 5cents: Typically I have a PY_ENV target in my projects, building a virtualenv in a folder named ./local. E.g. in LinuxDoc [1] I use something like this: PY ?=3 PYTHON ?= python$(PY) .. VIRTUALENV = virtualenv --python=$(PYTHON) VTENV_OPTS = "--no-site-packages" PY_ENV = ./local/py$(PY) .. quiet_cmd_virtualenv = PYENV $@ cmd_virtualenv = \ if [ ! -d "./$(PY_ENV)" ];then \ $(VIRTUALENV) $(VIRTUALENV_VERBOSE) $(VTENV_OPTS) $2; \ else \ echo "using virtualenv from $2"; \ fi ... # to build *local* environment, python and virtualenv from the OS is needed! $(PY_ENV): virtualenv-exe python-exe $(call cmd,virtualenv,$(PY_ENV)) @$(PY_ENV_BIN)/pip install $(PIP_VERBOSE) -r requirements.txt .. And the sphinxbuild coammand is used from there:: SPHINXBUILD ?= $(PY_ENV_BIN)/sphinx-build By this I can stick versions packages. E.g. to select last version of RTD theme and Sphinx version 1.5 or upper, I add the following lines to my reqierements.txt:: Sphinx>=1.5 sphinx_rtd_theme If you are interested, I can prepare a patch, to add such functionality (as option) to Documents/Makefile (which will be documented in the doc-guide). [1] https://github.com/return42/linuxdoc/blob/master/utils/makefile.python -- Markus -- > > jon > -- > To unsubscribe from this list: send the line "unsubscribe linux-doc" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] changes.rst: explain the usage of virtual environment Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-06-19 13:30 +0200
Re: [PATCH] changes.rst: explain the usage of virtual environment Christoph Hellwig <hch@infradead.org> - 2017-06-19 15:10 +0200
Re: [PATCH] changes.rst: explain the usage of virtual environment Jonathan Corbet <corbet@lwn.net> - 2017-06-19 15:50 +0200
Re: [PATCH] changes.rst: explain the usage of virtual environment Markus Heiser <markus.heiser@darmarit.de> - 2017-06-19 16:20 +0200
Re: [PATCH] changes.rst: explain the usage of virtual environment Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-06-19 16:40 +0200
Re: [PATCH] changes.rst: explain the usage of virtual environment Markus Heiser <markus.heiser@darmarit.de> - 2017-06-19 17:20 +0200
Re: [PATCH] changes.rst: explain the usage of virtual environment Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-06-19 16:30 +0200
csiph-web