←back to thread

89 points Numerlor | 6 comments | | HN request time: 0s | source | bottom
Show context
wodenokoto ◴[] No.41846571[source]
I feel like there’s a missing discussion as to why they aren’t going with Ipython
replies(7): >>41848474 #>>41851105 #>>41851125 #>>41851190 #>>41851214 #>>41852161 #>>41852289 #
1. 12_throw_away ◴[] No.41851214[source]
I'm sure it's for exactly the same reason that I'm often hesitant to install it - huge dependencies:

  $ pip show ipython
  [...]
  Requires: appnope, backcall, decorator, jedi, matplotlib-inline, pexpect, pickleshare, prompt-toolkit, pygments, stack-data, traitlets
replies(4): >>41851344 #>>41851347 #>>41853667 #>>41854096 #
2. 12_throw_away ◴[] No.41851344[source]
Also, I'm genuinely thrilled to see cross-pollination from pypy back to cpython, so am actually really glad they did it this way - as cpython's JIT becomes production-ready, maybe more bits of python will become be self-hosting?
3. boxed ◴[] No.41851347[source]
Also, jedi depends on parso. Parso does not yet support `match` (which is a big problem for me, as it means I need to switch AST library backing mutmut).
4. zahlman ◴[] No.41853667[source]
My guess is that it's not really designed to be fully severed from Jupyter. It certainly shouldn't require Matplotlib to run a console REPL.
replies(1): >>41854100 #
5. wodenokoto ◴[] No.41854096[source]
While I haven’t figured out how, it is my understanding that there exists a workflow where you have ipython/jupyter installed once, and then have them use the Python interpreter and modules associated with each project.

But I’ve never figured it out and instead have a `requirements-dev.txt` with Jupyter and Ipython in every project because they are so good to have on hand when developing

6. 0cf8612b2e1e ◴[] No.41854100[source]
I am pretty sure matplotlib is not required. That is just a convenience library that improves the notebook experience if matplotlib is loaded. So you no longer need to run the magic function ‘%matplotlib inline’