Maybe deprecate it for a release cycle and see if anybody complains once
they see the warning?
(also I am, in general, always in favor of simplifying things in nbconvert
:-) )
On Fri, Feb 15, 2019 at 5:56 PM Matthew Seal wrote:
> Do you think we should remove the functionality from nbconvert
Do you think we should remove the functionality from nbconvert to simplify
things there too?
On Thu, Feb 14, 2019 at 1:28 PM Samuel Lelièvre
wrote:
> Related: the latest version of nbconvert added defusedxml as a dependency.
>
> --
> You received this message because you are subscribed to the
I think this has more to do with network exposure of your container to your
machine unless I am mistaking the question. Jupyter is using a host and
port inside your container that may not map to the same host and port on
your machine.
Also, after some curious searching, I found this project, which may also help.
You would have to represent your Notebooks as a .py file, but perhaps that
would work for you: https://github.com/mwouts/jupytext
/Jason
From: jupyter@googlegroups.com on behalf of
Hi Alexander,
As I understand, you are looking for something that will take code and text
files in an existing Git repository and somehow automagically create a .ipynb
file from them. I am not aware of any project/tool out there that does exactly
what you want. However, the Jupyter Notebook
Hi. I am looking for a way to get a Jupyter notebook directly from the
information in a git repo. the idea is simply that the Jupyter is built
automatically from information in the git repo. it could for instance be by
taking text from the MD files, or having the specs for the Jupyter in a
