nbdev tutorial

preview_player
Показать описание
Рекомендации по теме
Комментарии
Автор

Been waiting for this video tutorial since nbdev was announced and since the fastai-v2 walkthroughs. Thanks so much for all you do!!

scottc
Автор

This helped me to catch a few things I otherwise have been missing. Thanks.

KonstantinDorichev
Автор

I am still having troubles with colab. I still don't know how to use some of the features.

Jimmypenguinboy
Автор

Thanks a lot! I have been wanting to do everything in Jupiter notebook and nbdev is a great tool! but it seems like package dependency is sit in settings.ini, if I choose to setup environment in virtualenv or pipenv, I need manually copy dependency into sittings.ini, is there any recommendation?

aiexplainai
Автор

Thanks to Jeremy and team for this practical resource!

MichaelJChoudhury
Автор

While the idea looks promising in the first place, and utmost awesome in the blog article, nbdev suffers from architectural flaws and plain bug plague, unfortunately. Guys, please rework this from the ground. The approach is great, and it definitely deserves better!

From the architecture perspective, the constant need to go to shell and leave the IDE-to-be to do this or that is a mess. Hey, that's just the promise of the "I" in "IDE" to *not* have to do that. Is there no way to include the necessary operations as a Jupyter extension like it's done with folding and TOC? It is also a problem that quite some bit of the framework is part of the template repo, so that is disconnected from any improvements of nbdev in the future. Using lots of undocumented defaults and conventions –which was already brought up in the video, and which is not better three months later– is also questionable. If it's good, why not make it part of the framework and document it properly, from the tutorial up?

The Return On Investment _may_ be worth all of that mess even without the necessary architectural corrections, but most users-to-be will never find out. And this is because of the bug plague. First, most of the coding bugs are still present in the "tutorial" code months after the video was done. Not a big deal, but just a glimpse of the sad truth that nbdev is composed not with usability, learning curve and quality in mind. I was naively just doing as outlined in the tutorial and am constantly hitting issue over issue. For example: The bootstrap stylesheet is not included in the <head> of the generated pages –in fact their <head> tag is empty– rendering them as plain vanilla text, which is not just not appealing, but almost unusable. To debug this, I next wanted to run Jekyll locally, but the installation as described rendered me with a 404 on port 4000. Do I need to mention that the makefile does forget to run the server in incremental mode? Guys, I mean, including docs from the beginning is the first and base promise of nbdev. Why do I have to debug this at all?

I admit that am starting to lose interest at this point to follow that debug the debug the debug process. Looking forward to the next release.

Else: great video :)

turkishmaid
Автор

Is there a 'go to definition' function?

geekypaul
Автор

How are you doing refactoring in these notebooks? Renaming a function and also all places where it is called? How can I find all places that call a function if I want to change stuff?

philipmay