In the SphinxBuilder, the command launched to start the build was using 'sphinx-build' and therefore retrieving the command from the PATH which is not robust with virtual/conda environments. Now, it uses the python interpreter that is used to run the script itself and use the '-msphinx_build' to call sphinx-build
Coverage remained the same at 76.068% when pulling 52b69f98cc58823cc0ac2eaaf36121300f33949a on sdementen:fix-virtual-conda-env into e0f40b6359ca00a48ca5ba903de1e25da27de453 on GaretJax:develop.
Coverage remained the same at 76.068% when pulling aaf117728d679cd631acf52938d11c4a50eed2fe on sdementen:fix-virtual-conda-env into e0f40b6359ca00a48ca5ba903de1e25da27de453 on GaretJax:develop.
Coverage remained the same at 76.068% when pulling aaf117728d679cd631acf52938d11c4a50eed2fe on sdementen:fix-virtual-conda-env into e0f40b6359ca00a48ca5ba903de1e25da27de453 on GaretJax:develop.
I'll close this PR since it's really old now and that PR is more up-to-date, and we need a bunch of bugfixes anyway. Thanks for filing this @sdementen! ^>^
In the SphinxBuilder, the command launched to start the build was using 'sphinx-build' and therefore retrieving the command from the PATH which is not robust with virtual/conda environments. Now, it uses the python interpreter that is used to run the script itself and use the '-msphinx_build' to call sphinx-build