JupyterLab 3.0
I don&#x27;t write Python code for my work. Last weekend I came across an interesting Jupiter notebook and figured I&#x27;d give it a try on my work laptop. &quot;It&#x27;s probably as easy as brew install pip and then use that to load the other dependencies,&quot; I assumed.<p>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, but it couldn&#x27;t find any dependencies for the notebook. As a complete newbie to the Python ecosystem, I googled for instructions and found various environment managers, which then failed possibly because something is incompatible with Big Sur. More googling revealed instructions with complex CFLAGS environment setups to fix it, which didn&#x27;t — and at that point it was very far from the supposed convenience of scripting languages anyway.<p>I don&#x27;t think it&#x27;s Python&#x27;s fault. Probably all the programming toolchains are this hard to a newbie! But it was a humbling experience after 34 years of programming, not being able to load a piece of sample code in a Sunday afternoon.