It has come to my attention that somebody ‘round these parts has been preaching the gospel of Sublime Text 3. Well, as the resident senior developer (err, old fogey), I feel it’s my duty to provide a counterexample by way of the only TRUE Python development environment you will ever need – and that environment is of course VIM. That’s right. VIM is ubiquitous, fast, and never crashes. And it can do just about anything!
On the down side though, VIM can be a pain to configure, but fear not – This article will show you how to get a powerful VIM environment setup, geared towards wrangling Python day in and day out.
To get the most out of this article you should have at least a basic understanding on how to use VIM and its command modes. If you’re just getting started, check out this resource or this one. Spend some time with it before moving on.
Since VIM comes pre-installed on a number of *nix systems, let’s first and foremost check to see if it’s installed:
If installed, you should see something like:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
At this point, you want to look for two things-
- The VIM version. This should be > 7.3.
- Python Support. Under the list of features, make sure you see
Grab Homebrew, if you don’t already have it, and run:
For Debian or Ubuntu you can try:
1 2 3
For other flavors of Linux check the docs from your package manager. Here is a link to get you started: Install Vim
There are many different ways to install VIM on Windows. Start with the official docs.
Verifying the Install
Make sure you have installed VIM > 7.3 with Python support. Again, run
vim --version to verify this. If you want to check the specific version of Python used in VIM, run
:python import sys; print(sys.version) from within VIM:
This should output your current version of Python. If you get an error, then you don’t have Python support and you either need to reinstall or recompile if you’re building from source.
With VIM installed, let’s look at how to customize VIM for Python development.
VIM can do a lot of what developers need right out of the box. However, VIM is also massively extensible and there are some pretty killer extensions that make VIM behave more like a “modern” IDE. So, the very first thing you need is a good extension manager.
Extensions in VIM are often referred to as bundles or plugins.
VIM has several extension managers, but the one we strongly recommend is Vundle. Think of it as pip for VIM. It makes installing and updating packages trivial.
Let’s get Vundle installed:
This command downloads the Vundle plugin manager and chucks it in your VIM bundles directory. Now you can manage all your extensions from the
.vimrc configuration file.
Add the file to your user’s home directory:
Now set up Vundle in your
.vimrc by adding the following to the top of the file:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
That’s it. You’re now set up to use Vundle. Afterward you can add the plugins you want to install, then fire up VIM and run:
This command tells Vundle to work its magic – downloading all the plugins and installing/updating them for you.
For Windows users, check out the Windows Installation Instructions.
Let’s make an IDE
We couldn’t possibly list all the VIM features, but let’s look at a quick list of some of the powerful out-of-the-box features perfect for Python development.
Ditch the Mouse
Probably the MOST important feature of VIM is that it doesn’t require a mouse (except for the graphical variants of VIM). At first this may seem like a horrible idea, but after you invest the time – and it does take time – to learn the key combinations, you will speed up your overall workflow!
Open a file with
:sv <filename> and you split the layout vertically (e.g., the new file opens below the current file) or reverse the keys to
:vs <filename> and you get a horizontal split (e.g., the new file opens to the right of your current file).
You can nest splits as well, so you can have splits inside of splits, horizontal and vertical, to your heart’s content. As we all know we often need to look at several files at once when developing.
Pro Tip: Make sure to utilize tab completion to find files after typing
Pro Tip: You can also specify different areas of the screen where the splits should occur by adding the following lines to the .vimrc file:
Pro Tip: Want to move between the splits without using the mouse? Simply add the following to .vimrc and you can jump between splits with just one key combination:
1 2 3 4 5
Ctrl-jmove to the split below
Ctrl-kmove to the split above
Ctrl-lmove to the split to the right
Ctrl-hmove to the split to the left
In other words, press
Ctrl plus the standard VIM movement key to move to a specific pane.
But wait what is the
nnoremapthing? – in a nutshell
nnoremapremaps one key combination to another; the no part means remap the key in normal mode as opposed to visual mode. Basically
nnoremap <C-J> <C-W><C-j>says in normal mode when I hit
<C-W><C-j>instead. More info can be found here.
While VIM can do tabs, many prefer buffers and splits. You can think of a buffer as a recently opened file. VIM provides easy access to recent buffers, just type
:b <buffer name or number> to switch to an open buffer (autocomplete works here as well). You can also use
:ls to list all buffers.
Pro Tip: At the end of the
:ls output, VIM will prompt with
Hit enter to continue. You can instead type
:b <buffer number> and pick the buffer immediately while you still have the list displayed (which saves a keystroke and having to remember the buffer number).
Most “modern” IDEs provide a way to collapse (or fold) methods and classes, showing you just the class/method definition lines instead of all the code.
You can enable that in .vimrc with the following lines:
1 2 3
This works all right, but you have to type
za to fold (and unfold). The space key would be much better. So add this line to your .vimrc file as well:
Now you can easily hide portions of your code that you’re not currently working on.
The initial command,
set foldmethod=indent, creates folds based upon line indents. This however often creates more folds that you really want. But have no fear! There are several extensions that attempt to rectify that. We recommend SimpylFold. Install it with Vundle by adding the following line to
Don’t forget to install the plugin –
Pro Tip: Want to see the docstrings for folded code?
Of course for code folding to work based on indentations, you want your indents to be correct. Again VIM falls short a bit out of the box because it doesn’t handle auto-indent after a function definition. Two things can be done with indentation:
- The first is to get indentation to follow PEP8 standards.
- The second part is to better handle auto-indentation.
To add the proper PEP8 indentation, add the following to your .vimrc:
1 2 3 4 5 6 7 8
This will give you the standard four spaces when you hit tab, ensure your line length doesn’t go beyond 80 characters, and store the file in a unix format so you don’t get a bunch of conversion issues when checking into GitHub and/or sharing with other users.
And for full stack development you can use another
au command for each filetype:
1 2 3 4
This way you can have different settings for different filetypes. There is also a plugin called ftypes which will allow you to have a separate file for each filetype you want to maintain settings for, so use that if you see fit.
Autoindent will help but in some cases (like when a function signature spans multiple lines), it doesn’t always do what you want, especially when it comes to conforming to PEP8 standards. To fix that, we can use the indentpython.vim extension:
Flagging Unnecessary Whitespace
We also want to avoid extraneous whitespace. We can have VIM flag that for us so that it’s easy to spot – and then remove.
This will mark extra whitespace as bad, and probably color it red.
For the most part, you should be using UTF8 when working with Python, especially if you’re working with Python 3. Make sure VIM knows that with the following line:
The best plugin for Python auto-complete is YouCompleteMe. Again, use Vundle to install:
Under the hood YouCompleteMe uses a few different auto-completers (including Jedi for Python), and it needs some C libraries to be installed for it to work correctly. The docs have very good installation instructions so I won’t repeat them here, but be sure you follow them.
It works out of the box pretty well, but let’s add a few customizations:
The former line ensures that the autocomplete window goes away when you’re done with it, and the latter defines a shortcut for goto definition.
My leader key is mapped to space, so
space-gwill goto definition of whatever I’m currently on. Helpful when exploring new code.
One issue with the goto definition above is that VIM by default doesn’t know anything about virtualenv, so you have to make VIM and YouCompleteMe aware of your virtualenv by adding the following lines of code to .vimrc:
1 2 3 4 5 6 7 8 9
This determines if you are running inside a virtualenv, and then switches to that specific virtualenv and sets up your system path so that YouCompleteMe will find the appropriate site packages.
You can have VIM check your syntax on each save with the syntastic extension:
Also add PEP8 checking with this nifty little plugin:
Finally, make your code look pretty:
Then just add a bit of logic to define which scheme to use based upon the VIM mode:
1 2 3 4 5 6
Solarized also ships with a dark and light theme. To make switching between them very easy (by pressing F5) add:
If you want a proper file tree then NERDTree is the way to go.
And if you want to use tabs, utilize vim-nerdtree-tabs:
Want to hide .pyc files? Then add the following line:
Want to search for basically anything from VIM? Check out ctrlP:
As expected, press
Ctrl-P to enable the search and then just start typing. If your search matches anything close to the file you’re looking for, it will find it. Oh – and it’s not just files; it will find tags as well! For more, check out this YouTube video.
Turn on line numbers on the side of the screen with:
Want to perform basic git commands without leaving the comfort of VIM? Then vim-fugitive is the way to go:
See it in action on VIMcasts.
Powerline is a status bar that displays things like the current virtualenv, git branch, files being edited, and much more.
It’s written in Python, and it supports a number of other environments like zsh, bash, tmux, and IPython.
Take a look at the official docs for all the configuration options.
Vim usually has its own clipboard and ignores the system keyboards, but sometimes you might want to cut, copy, and/or paste to/from other applications outside of VIM. On OSX, you can access your system clipboard with this line:
VIM in the Shell
And finally, once you’ve mastered VIM and its keyboard shortcuts, you’ll often find yourself getting annoyed with the lack of those same shortcuts in the shell. Fear not, most shells have a VI mode. To turn it on for your shell, add the following line to ~/.inputrc:
Now you will not only be able to use VIM key combos in the shell, but also in the Python interpreter and any other tool that uses GNU Readline (i.e., most database shells). Now you have VIM everywhere!
That’s more or less it (for Python development, at least). There are a ton of other extensions that you can use, as well as alternatives to everything detailed in this post. What are some of your favorite extensions? How have you configured VIM to match your personality?
Here is a link to my current VIM config. Got one of your own? Please share!
Thanks for reading!
- VIM Tutor comes with VIM, so once VIM is install just type
vimtutorfrom the command line and the program will teach you how to use VIM by, well, using VIM.
- VIMcasts are advanced tutorial videos describing how to use many of VIM’s features.
- Official VIM docs
- Open Vim
- Learn Vimscript the Hard Way is perfect for learning vimscript.