![]() Going forward I would suggest to use JupyterLab. go for it (and buy a large supply of painkillers upfront). Then again, many people and organizations also use a bunch of Excel-based macro's to run their critical business processes, so if you feel lucky. Just know it is (and never was) intended to be used for such. #Jupyter vs jupyterlab codeThat type of work is the main use-case of both (IMHO).įor writing 'robust, repeatable production grade' code I personally would not use Jupyter(Lab), although there is nothing holding you back to do that. Fixing such issues is most of the time a simple matter of installing an equivalent JupyterLab-ready extension and doing some small updates to your 'widget code'.īoth JupyterLab and Jupyter can be (and are being) used to 'quickly write a piece of code to test something and then throwaway' or 'do a quick analysis' or similar one-off pieces of code. Hence some 'classic Jupyter widgets' may not work as expected or at all. Interactive widgets / nbextensions (which are user interface type of functionalities) are treated differently in JupyterLab versus good old Jupyter. ipynb file) that was created using Jupyter in JupyterLab and vice-versa.Ī notable exception to this is (as u/william12323 remarks) when interactive widgets are used in the notebook file. This means that, in most cases, you can without any problem open and execute a notebook (the. To be clear: the differences are mainly on user interface level, what goes on behind the screens is essentially still the same. You can consider JupyterLab being the next version of the classic Jupyter interface, bringing new usage functionality and an improved user experience (well, that's the claim). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |