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

91–100 of 145 posts

Re: JupyterLab 3.0

#91

Post by p1esk »

bitanarch wrote: post #22
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,…

You should use Anaconda instead of pip to install data science related tools in Python. ``` $ conda create -n {new_environment_name} python $ conda activate {new environment name} $ conda install jupyterlab ```

    conda install -c conda-forge jupyterlab=3

Re: JupyterLab 3.0

#92

Post by syntaxing »

pavlov wrote: post #38
syntaxing wrote: post #24

Earlier quoted context omitted.

Always try using a virtual env. Also try using pip directly through ‘python3 -m pip install jupyter’ . Same to run it to bypass path issues ‘python3 -m jupyter notebook’. You should be up and running in a couple mins!

These were among the suggestions that I tried. I think the virtual env failed because of Big Sur, but not sure.

Hmm that’s super weird, M1 or Intel CPU? Also where does ‘which python3’ point to?

Re: JupyterLab 3.0

#93

Post by ChrisRackauckas »

jonathanyc wrote: post #90
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 find that everything in Jupyter-land is as inconvenient to reproduce as it is convenient to experiment with. Case in point: last I checked, you still had to do gymnastics in order to even store your notebooks in Git in a meaningful way (e.g. allowing merges). It really throws me off the whole thing (Julia + Jupyter is even worse...) because I’m not keen on putting effort into stuff that nobody, myself included, wil…

For Julia you might as well use Pluto (https://github.com/fonsp/Pluto.jl) or an IDE.

Re: JupyterLab 3.0

#95

Post by SatvikBeri »

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 use PyCharm + Jupyter Notebooks with autoreload. I'll build up functions in the notebook by running small bits of code, then move them to a Python file. It's like a supercharged version of a REPL.

VSCode's version is nice for sure, but not nearly as nice as being able to go back and read/modify old cells.

Re: JupyterLab 3.0

#96

Post by jonathanyc »

ChrisRackauckas wrote: post #93
jonathanyc wrote: post #90

Earlier quoted context omitted.

I find that everything in Jupyter-land is as inconvenient to reproduce as it is convenient to experiment with. Case in point: last I checked, you still had to do gymnastics in order to even store your notebooks in Git in a meaningful way (e.g. allowing merges). It really throws me off the whole thing (Julia + Jupyter is even worse...) because I’m not keen on putting effort into stuff that nobody, myself included, wil…

For Julia you might as well use Pluto ( https://github.com/fonsp/Pluto.jl ) or an IDE.

Thanks, I’ll check those out! It’s hard to know what’s recommended by the community sometimes. I was using Julia + Jupyter through CoCalc which is great for collaborating but the non reproducibility aspect was starting to raise alarm bells for me.

Re: JupyterLab 3.0

#97

Post by eggie5 »

bitanarch wrote: post #22
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,…

You should use Anaconda instead of pip to install data science related tools in Python. ``` $ conda create -n {new_environment_name} python $ conda activate {new environment name} $ conda install jupyterlab ```

why?

Re: JupyterLab 3.0

#99

Post by narush »

I'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 the release :)

Re: JupyterLab 3.0

#100

Post by sooheon »

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

> I have no idea to this day how macs became the premier development environment.

    s/macs/python
    s/development environment/scripting language
Post reply on HN