Ok this may be kind of stupid, but my primary reason for not switching over to jupyter lab (from notebooks) was the right-click menu wouldn't let me copy images (plotting outputs typically) from the in-line output. However I found out today that it has always been available if you hold shift...so if that was anyone's issue this is a great time to give JupyterLab another shot!
JupyterLab 3.0
121–130 of 145 posts
Re: JupyterLab 3.0
#122I don't write Python code for my work. Last weekend I came across an interesting Jupiter notebook and figured I'd give it a try on my work laptop. "It's probably as easy as brew install pip and then use that to load the other dependencies," I assumed. Over an hour later I had to give up. There was initially some kind of Python version conflict on my Mac. Eventually some version of JupyterLab was installed somewhere,…
Re: JupyterLab 3.0
#123I don't write Python code for my work. Last weekend I came across an interesting Jupiter notebook and figured I'd give it a try on my work laptop. "It's probably as easy as brew install pip and then use that to load the other dependencies," I assumed. Over an hour later I had to give up. There was initially some kind of Python version conflict on my Mac. Eventually some version of JupyterLab was installed somewhere,…
> I don't think it's Python's fault. Well, there's a long legacy of half-baked solutions and kludges. And, especially, install instructions consistently suggest you do the worst thing: install stuff using pip. Everyone knows that's bad advice, because it always fails in mysterious ways, and there's no good way to roll everything back. I recommend: python3 -m pip install pipx # Don't rely on the pip3 bin. pipx install…
Re: JupyterLab 3.0
#124Earlier quoted context omitted.
In a better world, the notebook you downloaded should have come with a list of dependencies and have reproducible code in it. That said, Python environment tools and package managers are still in a state of flux. Some tools make it easier, but are not helping much with reproducibility (plain venv + pip, but only if you got all required system packages installed!), other tools enable reproducibility, but have growing…
I talked to Fernando about this at Neuroinformatics 2018. In principle generating dependencies from a notebook should be as easy as parsing the ast, finding all the import statements, and then using sys to lookup what package provided that module. In practice I stopped using notebooks entirely due to many of the issues described by pavlov above, though in my case it was mostly because it was at a point in time where…
Then comes the point, where one of your dependencies in conda simply wont install on the machine of your coworker or a windows machine of another coworker, or in your docker image and you are screwed, scrambling for the next package manager. Been there, experienced that.
I can only recommend to people not to go that route and to not get into trying to get the same environment on windows. A lot of headaches. It will be simpler to tell people to use another OS, if they want to use the same environment. Ultimately I ended up providing a virtual machine.
A managed solution -- Yes, this takes a lot of load off of the shoulders of people, who would like to actually get productive in other ways.
Re: JupyterLab 3.0
#125I'm one of those extension developers that working on getting my extension working on JupyterLab 3.0 :-) I've been developing Mito ( https://trymito.io ), a spreadsheet extension to JupyterLab that allows you to edit a spreadsheet in a notebook as if you're editing Excel. You edit the spreadsheet, and Python code gets generated that corresponds to your edits. Feedback on the above greatly appreciated. And congrats on…
Re: JupyterLab 3.0
#126Earlier quoted context omitted.
In a better world, the notebook you downloaded should have come with a list of dependencies and have reproducible code in it. That said, Python environment tools and package managers are still in a state of flux. Some tools make it easier, but are not helping much with reproducibility (plain venv + pip, but only if you got all required system packages installed!), other tools enable reproducibility, but have growing…
> Python environment tools and package managers are still in a state of flux They've pretty much always been a moving target, haven't they? Nothing has ever been good enough that the community agrees "okay, this is it, we can stop churning on this tooling for a while".
Probably testing package managers is not a simple thing to do.
Re: JupyterLab 3.0
#127I don't write Python code for my work. Last weekend I came across an interesting Jupiter notebook and figured I'd give it a try on my work laptop. "It's probably as easy as brew install pip and then use that to load the other dependencies," I assumed. Over an hour later I had to give up. There was initially some kind of Python version conflict on my Mac. Eventually some version of JupyterLab was installed somewhere,…
Don't even try. Use docker, there are official pre-built images. It's easy: docker run -p 8888:8888 -v ~/Code/actual-project/:/home/jovyan jupyter/datascience-notebook Note ~/Code/actual-project/ is a git repo or a mounted Google Drive folder. Moving from one machine to an other is pain-free. [1] https://jupyter-docker-stacks.readthedocs.io/en/latest/using...
Instead, use: docker run -p 127.0.0.1:8888:8888
Re: JupyterLab 3.0
#128Just to say a big thank you to all those who have worked on JupyterLab. It's by far my favourite notebook interface and I think gets the balance between a clean interface and powerful features just about right. I just wish that the cloud providers would adopt it as the basis for their products.
It’s not a basis for their products but this is something https://colab.research.google.com/notebooks/intro.ipynb#rece...
I hope that these closed source commercial platforms give back something to the open source community around Jupyter once they get out of the red numbers.
Re: JupyterLab 3.0
#129Earlier quoted context omitted.
It’s not a basis for their products but this is something https://colab.research.google.com/notebooks/intro.ipynb#rece...
Jup, MS Colab is one of the many commercial Jupyter/IPython notebooks available. There are also Y-combinator startups like https://deepnote.com/ I hope that these closed source commercial platforms give back something to the open source community around Jupyter once they get out of the red numbers.
I get that they feel the need to add their own features (collaboration etc) to distinguish themselves but it would be so much better if they had settled on a single UI.
Re: JupyterLab 3.0
#130Earlier quoted context omitted.
> followed by random annoyances that remind you you are using inferior, non-GNU utilities: Well, you can switch to another ls in 10 seconds by "brew install gnutools" or some such. Not to mention the same arguments could be made for FreeBSD, commercial unices, etc. Come to think of it, I've been using Unix (including Linux) for 25 years, and never even occured to me to expect "ls my_dir -l" to work.
What do you do if you want to add extra arguments when your cursor's at the end? Navigate back near (not to) the beginning? I usually just put them at the end, as almost every program I've used supports it. I add extra arguments after running commands constantly; after pressing up to get it back, you're at the end.
Yes. In most shells it's trivial to go back by a word (e.g. skip in front of the path with one shortcut).
That said, this happens so rare that it's not even something that ever registered with me as a problem. I know what arguments I want for ls. And if I don't it's usually some bizarro infrequent flag that I have to look up how it's used anyway.
And other programs where it would be actually useful don't allow it anyway (having flags after the "main" argument). Git, for one.