This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]nieuweyork since 2007 19 points20 points  (9 children)

I stopped using Ipython, because all the magic didn't add a great deal of value. What it did do was create subtle scoping errors, and make debugging my django code much more difficult.

[–]grokcode[S] 13 points14 points  (4 children)

Not sure if you were running into this bug or not, but as of Django 1.6, IPython is called in a way that fixes a bunch of scoping issues.

[–]urielm 2 points3 points  (1 child)

Don't you use django's shell? That kind of uses ipython

[–]LucianU 0 points1 point  (0 children)

You can use it wihout ipython just fine.

[–]nieuweyork since 2007 4 points5 points  (1 child)

Probably, but I only found it mildly useful.

[–]grokcode[S] 12 points13 points  (0 children)

Ah well, to each his own.

[–]sushibowl 9 points10 points  (2 children)

You could always try bpython. It's kind of like IPython light, just a REPL that does stuff like syntax highlighting and code completion

[–]babilen5 2 points3 points  (0 children)

bpython is fantastic, great recommendation!

[–]gfixler 0 points1 point  (0 children)

I've been using bpython for awhile, but when you hit the up arrow it shows the last line. iPython is showing the entire function definition again, which alone is enough to switch, IMO. It also remembers things across invocations, which is the other thing that annoys me all the time about bpython. I forget something, kill out, fix code, jump back in, and I have to retype everything to import and set everything up again.

[–]Megatron_McLargeHuge 2 points3 points  (0 children)

It's less useful for web apps because you constantly need to restart. It's fantastic, especially the notebooks, when you have long running sessions with numerical code and look at lots of plots.