From: Markus Heiser <markus.heiser@darmarit.de>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Bird, Tim" <Tim.Bird@sony.com>, Jonathan Corbet <corbet@lwn.net>,
"tbird20d@gmail.com" <tbird20d@gmail.com>,
"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: Wed, 4 Mar 2020 10:20:34 +0100 [thread overview]
Message-ID: <c491adf3-ae49-fefc-ea6d-32b75f4f9ca9@darmarit.de> (raw)
In-Reply-To: <20200304093138.6aced5a0@coco.lan>
Am 04.03.20 um 09:31 schrieb Mauro Carvalho Chehab:
> Em Wed, 4 Mar 2020 07:20:48 +0100
> Markus Heiser <markus.heiser@darmarit.de> escreveu:
>> With py3 the recommended way to install virtual environments is::
>>
>> python3 -m venv sphinx-env
>>
>> This (python3) is what worked for me on RHEL/CentOS (dnf),
>> archlinux and debian/ubuntu (tested from 16.04 up to 20.04).
>
> Hmm... from:
>
> https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/
>
> This works since Python version 3.3. It sounds doable to use it.
>
> Yet, if we'll be switching to this method, the script should check if
> the version is 3.3 or newer. The logic inside get_sphinx_fname() would
> also require some changes, as it won't need to install anymore the
> virtualenv program for Python >= 3.3.
I guess you can ignore 3.2 and downwards
https://en.wikipedia.org/wiki/History_of_Python#Table_of_versions
Support for py2.7 and >=py3.3 should match nearly all use cases / distributions
we support.
BTW: starting scripts with:
-m <module-name>
Searches sys.path for the named module and runs the
corresponding .py file as a script.
is mostly more robust. The option exists also in py2. From py3.3 on
a subset of virtualenv is built-in, so you can run '-m venv' ot of the
box.
-- Markus --
next prev parent reply other threads:[~2020-03-04 9:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 1:34 tbird20d
2020-03-02 20:09 ` Jonathan Corbet
2020-03-03 17:07 ` Bird, Tim
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 [this message]
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=c491adf3-ae49-fefc-ea6d-32b75f4f9ca9@darmarit.de \
--to=markus.heiser@darmarit.de \
--cc=Tim.Bird@sony.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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
all inboxes | Powered by JetHome®