That restriction looks like a generic safeguard based on semantic 
versioning. With semantic versioning, a new major version indicates an 
incompatible API change. So somebody will have to look into it and adapt to 
the breaking changes, or at least verify that everything still works. I 
guess that nobody got around to doing that for nbconvert with pandoc 2.0 - 
at least until recently...

https://github.com/jupyter/nbconvert/pull/933

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/6cc46be3-ecbc-464b-a9d9-20e538c86fe5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to