From a70df3c8775b9f55fd9cadc31b36a9f3c5ab509a Mon Sep 17 00:00:00 2001 From: Brecht Machiels Date: Wed, 10 Feb 2021 18:56:17 +0100 Subject: [PATCH] Docs: remove outdated notes on Windows compatibility (#382) * Docs: remove outdated notes on Windows compatibility Closes #379 * Docs: add Python Launcher notes to config section --- docs/config.rst | 11 ++++++++++- docs/usage.rst | 17 ----------------- 2 files changed, 10 insertions(+), 18 deletions(-) diff --git a/docs/config.rst b/docs/config.rst index 14b17da1..99580d17 100644 --- a/docs/config.rst +++ b/docs/config.rst @@ -88,7 +88,7 @@ Configuring a session's virtualenv By default, Nox will create a new virtualenv for each session using the same interpreter that Nox uses. If you installed Nox using Python 3.6, Nox will use Python 3.6 by default for all of your sessions. -You can tell Nox to use a different Python interpreter/version by specifying the ``python`` argument (or its alias ``py``) to ``@nox.session``: +You can tell Nox to use a different Python interpreter/version by specifying the ``python`` argument (or its alias ``py``) to ``@nox.session``: .. code-block:: python @@ -96,6 +96,15 @@ You can tell Nox to use a different Python interpreter/version by specifying the def tests(session): pass +.. note:: + + The Python binaries on Windows are found via the Python `Launcher`_ for + Windows (``py``). For example, Python 3.9 can be found by determining which + executable is invoked by ``py -3.9``. If a given test needs to use the 32-bit + version of a given Python, then ``X.Y-32`` should be used as the version. + + .. _Launcher: https://docs.python.org/3/using/windows.html#python-launcher-for-windows + You can also tell Nox to run your session against multiple Python interpreters. Nox will create a separate virtualenv and run the session for each interpreter you specify. For example, this session will run twice - once for Python 2.7 and once for Python 3.6: .. code-block:: python diff --git a/docs/usage.rst b/docs/usage.rst index 098609f2..bca73f39 100644 --- a/docs/usage.rst +++ b/docs/usage.rst @@ -346,23 +346,6 @@ You can output a report in ``json`` format by specifying ``--report``: nox --report status.json -Windows -------- - -Nox has provisional support for running on Windows. However, depending on your Windows, Python, and virtualenv versions there may be issues. See the following threads for more info: - -* `tox issue 260 `_ -* `Python issue 24493 `_ -* `Virtualenv issue 774 `_ - -The Python binaries on Windows are found via the Python `Launcher`_ for -Windows (``py``). For example, Python 3.5 can be found by determining which -executable is invoked by ``py -3.5``. If a given test needs to use the 32-bit -version of a given Python, then ``X.Y-32`` should be used as the version. - -.. _Launcher: https://docs.python.org/3/using/windows.html#python-launcher-for-windows - - Converting from tox -------------------