Matt McKay

@shlff I think this might be related to #226

I am also in favour of `{proof:ref}` as it binds to other `{proof:}` more clearly and makes reading the source markdown easier in my view. Can you give an example...

oh I see -- that's a nice idea.

thanks for reporting this issue @martinlarsalbert

@AakashGfude this will be a blocker for upgrading `jupyter-book` to support the latest `myst-nb` so we should try and prioritise this one.

@jlperla thanks for opening this issue. I have opened this issue https://github.com/QuantEcon/sphinx-tojupyter/issues/36

@jstac I will trigger a `coverage` run today. It is currently setup to only trigger once there is a change on `master` branch. It then runs `coverage` and `website` builds.

@jstac I have just updated this PR https://github.com/QuantEcon/lecture-source-py/pull/544 I think the next thing to work on is: 1. compilation on `travis` or `Docker` so we can keep upgrading anaconda and...

I have triggered `coverage` builds on `workstation` and `ec2` to check the latest. `EC2` has the latest `anaconda=2019.07`

@shizejin would you have any time available to review: - [ ] coase - [ ] change_ramsey - [ ] change_credible lectures in the `python-advanced` set of lectures. They are...