Skip to main content

PyCon: IPython: Getting the Most out of Working Interactively in Python

IPython is an amazing replacement for the standard Python shell. As a result of this talk, I've already switched.
  • It's embeddable so that you can add a shell into your existing applications.
  • You can even use it as a replacement for your UNIX shell because it's so easy to interact with UNIX command line utilities.
  • He mentioned "ipython -p tutorial", but I can't figure out what it does.
  • It has better introspection, tab completion, color, syntax highlighting, and debugger integration.
  • It was inspired by Mathematica.
  • It has macros.
  • It takes care of moving content to and from your editor so you don't have to cut and paste and remove the ">>>" at the beginning of each line.
  • It can trivially lookup code definitions and docs while you're working on something.
  • It has a better version of the "dir" function.
  • It has various, useful "magic" commands.
  • Doing things like "!ls" lets you talk to the shell. In this way, it's easy to do some UNIX shell scripting.
  • It has support for timing and profiling.
  • It has a nicer version of pdb called ipdb.
  • In stack traces, it can show the syntax highlighted code as well as all the data.
  • You can use ipython to dynamically code GUIs that have event loops that would block the normal interpreter.
  • In general, ipython knows how to work with the event loops of many different libraries.
Labels:

Comments

Anonymous said…
Q: He mentioned "ipython -p tutorial", but I can't figure out what it does.
A: It takes care of the ">>>" and "..." at the beginning of each line.
5:11 AM
Anonymous said…
Makes it really useful to cut-and-paste examples!
8:54 PM
Post a Comment

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe
1 comment
Read more

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo
50 comments
Read more

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p
66 comments
Read more