Describe the bug
Followed the steps provided in the main book:

Error log is attached.
error.txt
To Reproduce
Steps to reproduce the behavior:
All the files downloaded from github: https://executablebooks.github.io/quantecon-mini-example/docs/index.html
Error occurs runningjb build ./mini_books
thanks for reporting @denigomonov I wasn't able to recreate the issue in the error.txt but I have just submitted an update to the environment.yml for that repository as I was getting an incorrect version of sphinx.
Would you mind to try the latest version of quantecon-mini-example and let me know if you still get the same error.
Note I have also just released v0.7.5
thanks for reporting @denigomonov I wasn't able to recreate the issue in the
error.txtbut I have just submitted an update to the environment.yml for that repository as I was getting an incorrect version ofsphinx.Would you mind to try the latest version of quantecon-mini-example and let me know if you still get the same error.
I'll try now
@chrisjsewell @mmcky
Unfortunetly, it's not working - please review:
Encoding error:
'charmap' codec can't encode character '\u03b8' in position 6764: character maps to <undefined>
error_buildexample_jb.txt
I get the same error, but as I mention in executablebooks/quantecon-mini-example#31 it's really a corner case (I've never written python with greek letter variables myself). What does work for me is to activate the qe_dev environment in this file:
https://github.com/eoas-ubc/quantecon-mini-example/blob/windows_dev/environment_dev.yml then clone
https://github.com/executablebooks/jupyter-book, cd to the jupyter-book folder, and do
jb buid docs
which produces a formatted html book in docs\_build\html -- as long as you stick to the structure of the docs you should be ok.
Thanks for the update @denigomonov - this repo is a test case and is building via CI so I will dig into this a bit more today and see if I can replicate the new issue.
@mmcky -- I think it's just a pinning problem. The bug is fixed in jupyter-sphinx 0.3.0a1 but something has a hard pin to 0.2.4. The correct commit to use is the @foster999 fork I reference in https://github.com/eoas-ubc/quantecon-mini-example/blob/windows_dev/environment_dev.yml. The full traceback is https://github.com/eoas-ubc/quantecon-mini-example/blob/windows_dev/sphinx-err-nmgmp4wy.txt
Yeh myst-nb is currently pinned to v0.2.
I've pestered @akhmerov about this a little already but can you release a final v0.3.0 please, so I can update the pinning 馃槵 馃檹, or is there any blockers?
Will do.
I would like to include https://github.com/jupyter/jupyter-sphinx/issues/126 in the release, and I hope to address it in the next couple of days (it breaks too much stuff).
Thanks 馃槃
0.3.0 on pypi, conda pending
Which would be great, if you hadn't broken the whole of sphinx 馃槅 馃槶
Somehow with jupyter-sphinx v0.3
this:

Now gives:
/Users/chrisjsewell/Documents/GitHub/MyST-NB-actual/docs/examples/basic.md:48: WARNING: image file not readable: examples/examples/../_static/logo.png
0.3.0 0.3.1 :innocent:
thanks for the updated jupyter-sphinx @akhmerov
Even if it is still slightly broken 馃槣 https://github.com/jupyter/jupyter-sphinx/pull/159
At least this limitation wasn't introduced in 0.3 :rofl:
This should be closed in v0.8.0 馃槃, but feel free to re-open/open another issue if anything is outstanding: https://jupyterbook.org/reference/_changelog.html#v0-8-0-2020-09-01
Most helpful comment
0.3.00.3.1 :innocent: