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

JupyterLab is ready for users

blog.jupyter.org

Post reply on HN
Print view View original

131–140 of 250 posts

Re: JupyterLab is ready for users

#131

Post by goerz »

carreau wrote: post #126
goerz wrote: post #123

I very heavily rely on the "official" notebook extensions from https://github.com/ipython-contrib/jupyter_contrib_nbextensi... This especially includes things like "Table of Contents", "Variable Inspector", "Ruler", and "Execute Time". How easy will it be to have all of this functionality in the JupyterLab notebooks? There's certainly advantages to having data/terminals/notebooks in an IDE-style layout, but for the m…

First of all these are not "official" (hence why it's a different organisation on GitHub) and all is maintained by community. It will take some time to port all the existing extensions, but the good news is that JupyterLab has been thought to work with extensions (actually everything in JupyterLab is an extension with no privileged component), so it will be easier to write these for JupyterLab than for current notebo…

Will do! And thanks for all the great work around the Jupyter ecosystem. I didn't mean to come across as too critical!

Re: JupyterLab is ready for users

#132

Post by monkmartinez »

carreau wrote: post #71
monkmartinez wrote: post #60

There is only one mention of Python in the entire post... there are 5 mention of JavaScript. Recently, I have been mulling over the GUI creation problems and packaging problems that still plague the Python ecosystem. That being just the start of it... I guess my love affair with Python is souring a bit. Compared to JavaScript it seems like it has slowed to a crawl on the innovation front. That is, for anything NOT re…

Haha, don't worry the Python side is still quite active, and IPython is still evolving. JupyterLab is (so far) only a new UI. It still connects to all the kernels via the same protocol in the back, and we were not willing to change both at the same time. But thanks for caring and expressing concerns.

The fact that the GUI is written in JS is my point. The reports of Python's death... you heard it here first.

Re: JupyterLab is ready for users

#133

Post by monkmartinez »

danielvf wrote: post #46

I'll be teaching a group of nine and ten years olds to code. I'm planning on using Jupyter. What I'd really like to do is make a multiplayer naval game, with each player controlling their ship from their own notebook. Players would start out by running commands like fire(range=400, bearing=120) right from a cell, but would later be able automate their ship - for example, pick the nearest enemy, get the range, and plu…

> Any advice on how to do this in Juptyer with Python? In an ideal world, I'd just "tag" a cell somehow so that it ran periodically.

Don't. Use something that will engage them visually and mentally. Kids are not impressed with text, that ship has sailed.

Re: JupyterLab is ready for users

#134

Post by jasongrout »

in9 wrote: post #115
danielvf wrote: post #46

I'll be teaching a group of nine and ten years olds to code. I'm planning on using Jupyter. What I'd really like to do is make a multiplayer naval game, with each player controlling their ship from their own notebook. Players would start out by running commands like fire(range=400, bearing=120) right from a cell, but would later be able automate their ship - for example, pick the nearest enemy, get the range, and plu…

To be totally honest, even though I love Jupyter notebooks, I wouldn't teach someone to code using it. See, as someone who's not, originally a programmer, I believe that teaching someone to code is intertwined with teaching (gradually) workflows and environments. Now, Jupyter is great (I'm a statistician btw) precisely because you have a presentable literate programming tool. That is extremely valuable for data analy…

I'm teaching someone to code right now on the Raspberry Pi, and JupyterLab is working far better for us than IDLE or a separate text file and terminal. We use the workflow described in http://jupyterlab.readthedocs.io/en/stable/user/documents_ke.... We open up our python file and a console side-by-side, and pressing shift-enter in the file sends a line or selection to a console. We can easily investigate it in the console outside of the file too.

You can just "pip install jupyterlab" on a Raspberry Pi and it works great!

Re: JupyterLab is ready for users

#137

Post by asafira »

Quenty wrote: post #30

If you like Juypter, Google colabs has a google-docs style juypter notebook that’s quite good. It’s nice for collaboration. https://colab.research.google.com/notebook

How much public information is there about how much support this will get outside of Google?

Re: JupyterLab is ready for users

#138

Post by Wehrdo »

isaiahg wrote: post #103
afshin wrote: post #90

Earlier quoted context omitted.

The closest thing to what you're asking for is the first image in the post, which is a screenshot that has this caption: > JupyterLab is an interactive development environment for working with notebooks, code, and data.

But what are jupyter notebooks? Had to Google it to find out. Still not sure what it does.

This isn't meant to be snarky, but maybe this post just isn't for you, in the same way that posts about Ruby on Rails simply aren't for me.

On the other hand, if you use Python, you should definitely check out Jupyter notebooks (formerly IPython notebooks, and now JupyterLab, I guess). They're useful when prototyping data pipelines, since the state of the interpreter is saved, letting you iterate on ideas and see the outputs quickly.

Re: JupyterLab is ready for users

#140

Post by carreau »

goerz wrote: post #131
carreau wrote: post #126

Earlier quoted context omitted.

First of all these are not "official" (hence why it's a different organisation on GitHub) and all is maintained by community. It will take some time to port all the existing extensions, but the good news is that JupyterLab has been thought to work with extensions (actually everything in JupyterLab is an extension with no privileged component), so it will be easier to write these for JupyterLab than for current notebo…

Will do! And thanks for all the great work around the Jupyter ecosystem. I didn't mean to come across as too critical!

Didn't meant to imply you were critical, sorry if it's how I expressed myself. Just trying to explain what did not ended in the blog post. Thanks!
Post reply on HN