But there is a valid point in there. import cv2
as a single cell in a notebook causes your conversion tool to fail though with ModuleNotFoundError: No module named 'cv2'
. I think “If missing, packages will be inferred from the notebook’s content”, may be misleading.
Furthermore, if I add opencv-python
to requirements.txt
and upload that along with the notebook with just that cell, then it still fails it seems with 404 error. opencv-python
is in pyodide and so I don’t see why that would not work. … Oh wait, that may not be unusual…
Maybe more indicative of deeper problems, and explaining above, I submit the following…
If I take your test notebook code & the requirements.txt file and upload those myself to your tool, that doesn’t work. It just links to 404 Not Found. That code came from here
Example URL of one of my attempts at that:
https://nb2dash.ploomberapp.io/notebook/0848d835/lab/index.html
I do note that doesn’t look like the voici render URL your example uses, which is:
https://nb2dash.ploomberapp.io/notebook/bb8086c0/voici/render/notebook.html
Note the voici/render/
vs what you link gives of /lab
? Not the same pattern.
I probably should also mention to help you in maybe troubleshooting:
If I left out the requirements.txt
for your demo notebook and just uploaded it. It works to launch a voici render. And the link provided by the tool matches the pattern of your demo, too.
Demo URL result from not including requirements.txt
.
https://nb2dash.ploomberapp.io/notebook/bb500a66/voici/render/notebook.html
Of course, without the requirements.txt
though, it errors out when it does try to run.
Wait, I think you give the first part and it adds later part:
https://nb2dash.ploomberapp.io/notebook/269fe9e4
forwards to https://nb2dash.ploomberapp.io/notebook/269fe9e4/voici/render/notebook.html
So I don’t get why including a requirements.txt
changes that forwarding for your provided demo example when I try it? And changing the URL doesn’t help if I do it by hand when I included a requirements.txt
.