Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JupyterLab 3.0

blog.jupyter.org

Post reply on HN
Print view View original

61–70 of 145 posts

Re: JupyterLab 3.0

#61

Post by coldtea »

pavlov wrote: post #14

I 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.

Actually it is:

https://xkcd.com/1987/

That said, you would be up and running if you used conda.

And this is not the usual "just try distro X" Linux advocate BS when somebody has an issue with distro Y.

Conda does makes thing more user friendly by focusing on whole environments. Actually that's why it was built for.

Note that this applies for this situation. For other uses cases, e.g. deploying something to production, having used conda would have made your life more difficult.

Re: JupyterLab 3.0

#62

Post by klelatti »

ahupp wrote: post #56
klelatti wrote: post #32

Earlier quoted context omitted.

Could you share any examples of what you've seen?

This one uses JupyterLab as a frontend for CadQueury, a porcedural CAD system. https://github.com/bernhard-42/jupyter-cadquery

Thank you that's really interesting. I've been working on a (proprietary) project that uses JupyterLab as a front end - for actuarial / insurance calculations. Happy to share experiences even if I can't share the underlying code (which probably wouldn't be of interest anyway!).

Re: JupyterLab 3.0

#63

Post by coldtea »

typomatic wrote: post #20
pavlov wrote: post #14

I 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 have used Python on OSX for years and it is and always will be a horrorshow. Using the system Python installation is a nonstarter for many reasons, chief among them is that I don't have any interest in using py2. So then you're using pyenv or homebrew, but your vim install still thinks that it should be using the system python. And whoops, you fixed that and now virtualenv is not finding your interpreter. And etc.,…

>OSX and its tooling are just ridiculous. I have no idea to this day how macs became the premier development environment.

Because:

(a) it's quite easy to set things up with brew, macports, and/or Nix

(b) because Python is shitty everywhere anyway, and Python isn't the be-all end-all of development work.

(c) because you get a full-featured, working, coherent, take-it-or-leave-it desktop that stops one way of endless tinkering and procrastinating available in Linux to get things "just right"

(d) because it's still a UNIX with a full support for unicy tools, not a hack like WSL or WSL2.

(e) because it has good hardware (mostly - BS keyboard-era aside) and good resale value

(f) because you get to enjoy most/all the proprietary tools you like too (from MS Office and Adobe Creative Suite, to whatever)

(g) because in 2020 Docker, remote environments, etc, make many "local dev environment" points moot anyway

Re: JupyterLab 3.0

#64

Post by coldtea »

sangnoir wrote: post #52
jackson1442 wrote: post #33

Earlier quoted context omitted.

> I have no idea to this day how macs became the premier development environment. I've been editing a tutorial one of my coworkers wrote that targets new Python users on Windows. From my findings, the grass is not greener. Granted, geospatial Python is somewhat of a mess, but a lot of tools I have to use are somewhat messy forks of Unix tools (looking at you, pyenv-win) with tons of incompatible extensions. For devel…

> I've been editing a tutorial one of my coworkers wrote that targets new Python users on Windows. From my findings, the grass is not greener. Maybe check the other other side (Linux) - I found the grass is greener there - at least for Python (and programming tools in general). I'm very comfortable on the command-line, and moving from a pure Linux environment to OS X & brew felt like a huge downgrade, followed by ran…

>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.

Re: JupyterLab 3.0

#65

Post by philsnow »

zelphirkalt wrote: post #53
pavlov wrote: post #14

I 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,…

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".

Re: JupyterLab 3.0

#66

Post by hnews2 »

klelatti wrote: post #32
hnews2 wrote: post #27

I've seen a few projects that have used the JupyterLab UI for other projects as a simple interface - it looks really neat and slick. I just wondered if anyone has any ideas how you go about this as I've been drawing a blank.

Could you share any examples of what you've seen?

I'm so sorry, I don't remember - I had a demo of an app about 6 months ago which went no where, but, the interface was amazing and they told me they used the Jupyter project's interface.

I tried downloading the source and removing the majority of the bits, but, I just got absolutely nowhere and was hoping there was a library somewhere or a guide that would make this job much easier, however, I'm getting nowhere!

Re: JupyterLab 3.0

#67

Post by philsnow »

baldfat wrote: post #37
pavlov wrote: post #14

I 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,…

Python is AMAZING and Awesome TILL You want to spread what you are doing to more then one computer. Though I have to say I love domain specific languages and personal enjoy Racket as my most fun language to use. It is sad that this has gotten so much worse over the years.

re:re:re:

  A: it works on my computer
  B: then we'll ship your computer
  and that's how docker was born

Re: JupyterLab 3.0

#68

Post by klelatti »

hnews2 wrote: post #66
klelatti wrote: post #32

Earlier quoted context omitted.

Could you share any examples of what you've seen?

I'm so sorry, I don't remember - I had a demo of an app about 6 months ago which went no where, but, the interface was amazing and they told me they used the Jupyter project's interface. I tried downloading the source and removing the majority of the bits, but, I just got absolutely nowhere and was hoping there was a library somewhere or a guide that would make this job much easier, however, I'm getting nowhere!

Thanks. Do you remember what was amazing? I've been using a fairly vanilla JupyterLab setup as the basis for a (proprietary) project. I've found the docs generally OK for what I've been doing.

To be honest one of the worst things about JupyterLab I've found is the number of interesting extensions that look great but turn out to be unmaintained or overlap with others. It can be really confusing!

Re: JupyterLab 3.0

#69

Post by jVinc »

klelatti wrote: post #57
bobbylarrybobby wrote: post #42

I don't understand why Jupyter notebooks are still in use as a writable format when there are editors like VSCode that can treat ordinary python files as notebooks. The Python extension can submit code blocks to the kernel and import and export Jupyter notebooks, but VSCode is also a real editor on top of that (debugging, git, vim mode, hover info, etc.). For distribution, as a read-only format (like PDF), notebooks…

I think you're suggesting that if you want to retain both code and results you need to manage two different files - raw python and exported notebook. I think many notebook users would see that as inconvenient (and many are not familiar with VSCode).

Jupyterlab has an extention that does this automatically on save, jupytext, also keeps both files in sync over time.

Re: JupyterLab 3.0

#70

Post by hnews2 »

klelatti wrote: post #68
hnews2 wrote: post #66

Earlier quoted context omitted.

I'm so sorry, I don't remember - I had a demo of an app about 6 months ago which went no where, but, the interface was amazing and they told me they used the Jupyter project's interface. I tried downloading the source and removing the majority of the bits, but, I just got absolutely nowhere and was hoping there was a library somewhere or a guide that would make this job much easier, however, I'm getting nowhere!

Thanks. Do you remember what was amazing? I've been using a fairly vanilla JupyterLab setup as the basis for a (proprietary) project. I've found the docs generally OK for what I've been doing. To be honest one of the worst things about JupyterLab I've found is the number of interesting extensions that look great but turn out to be unmaintained or overlap with others. It can be really confusing!

It just worked!

Basically, we build a lot of internal webapps and it's so common that you need to compare x against y, go back and forth between screens...

Most users simply open up multiple tabs and view side by side.

To me, if we could easily have the interface setup so that every object opens in a new "window" with the ability to dock side by side/navigate independently, I just feel it is much neater than the standard admin templates we use on a daily basis.

Truthfully, I've not spent ages looking in to this, but, I did spend a few hours with the Jupyterlabs code and I just got nowhere.

Basically, I would love to just get a page up, the full Jupyter interface, standard menu bar to the left or on top and the ability to just load multiple "Hello World" pages in separate windows.

Post reply on HN