@@ -6,65 +6,7 @@ Jupyter Book is now also tested against a Windows environment on Python 3.7 😀
For its specification, see the [`windows-latest` runner](https://docs.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners#supported-runners-and-hardware-resources) used by GitHub CI.
However, there is a known incompatibility for notebook execution, when using Python 3.8
(see issue [#906](https://github.com/executablebooks/jupyter-book/issues/906)).
(see this jupyter issue:[jupyter/nbclient#85](https://github.com/jupyter/nbclient/issues/85))
If you're running a recent version of Windows 10 and encounter any issues, you may also wish to try
If you're running a recent version of Windows 10 and would like to build with Python 3.8 or encounter issues not covered in the tests, you may also wish to try
[installing Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/install-win10).
As of June 5, 2020, there were three open issues that required Windows-specific changes.
We hope these are now fixed in version 0.8 of Jupyter Book but, in case any issues still arise,
we leave these community tips, which are known to work for some users.
Note that there is no guarantee that they will work on all Windows installations.
1. Character encoding
Jupyter Book currently reads and writes files on Windows in the native Windows
encoding, which causes encoding errors for some characters in UTF8 encoded
cmd.exe or powershell enviroments that set PYTHONUTF8=1 override the native
locale encoding and use UTF8 for all input/output.
:::{tip}
To make it easier to use this option,
the EOAS/UBC notebook courseware project has created a Conda package [runjb](https://anaconda.org/eoas_ubc/runjb) which [does this automatically for powershell](https://github.com/eoas-ubc/eoas_tlef/blob/master/converted_docs/wintools/binwin/runjb.ps1)
:::
2. A new Windows event loop
The asyncio event loop [has been changed for Python 3.8](https://github.com/sphinx-doc/sphinx/issues/7310)