Updated December 15, 2017
Hi! I’m Geoff Hing, a news applications developer who was filling in for Juan Elosua while he was on family leave welcoming his child into the world. Matthew Zhang started as the team’s intern around the same time, and as we wrap up our time out NPR, we’re also adding a few notes about how we’ve set up our development environments. This guide helps you get a solid Python environment set up, which we use for daily graphics, data analysis and application development.
I joined the News Apps team a week ago in their shiny new DC offices, and in-between eating awesome food and Tiny Desk concerts, we’ve been documenting the best way to get other journalists setup to build news apps like the pros.
The following steps will help you convert your laptop to hacktop, assuming you’re working on a new Mac with macOS 10.12, or Sierra, installed. Each Mac operating system is a little different, so we’re starting from scratch with the latest OS.
Chapter 0: Prerequisites
Are you an administrator?
We’ll be installing a number of programs from the command line in this tutorial, so that means you must have administrative privileges. If you’re not an admin, talk with your friendly IT Department.
Click on the Apple menu > System Preferences > Users & Groups and check your status against this handy screenshot.
Update your software
Go to the App Store and go to the updates tab. If there are system updates, install and reboot until there is nothing left to update.
Install command line tools
With the release of macOS 10.9, Apple decoupled its command line tools necessary for compiling some of the tools we use from Xcode, Apple’s proprietary development suite.
All Macs come with an app called “Terminal.” You can find it under Applications > Utilities. Double click to open that bad boy up, and run this command:
Your laptop should prompt you to install the command line tools. Install the tools and move on once that process has completed (about 5 minutes).
If it doesn’t install, or there isn’t an update for Xcode to install the tools, you’ll have to download the command line tools from developer.apple.com/downloads/index.action. You have to register, or you can log in with your Apple ID.
Search for “command line tools,” and download the package appropriate to your version of macOS. Double click on the .dmg file in your downloads file, and proceed to install. In my case, I downloaded Command Line Tools (macOS Mavericks), which is highlighted in the screenshot above.
Note: If you ever run into some variation of a ‘user does not have permission’ error when running a command in the terminal, prefix the command with
sudo. For example, the above command would be run as:
sudo xcode-select --install
After you enter in your administrator password, these installations should proceed as normal. You shouldn’t have to encounter this problem much in the following steps, but it’s good to know just in case.
Chapter 1: Install Homebrew
Homebrew is like the Mac app store for programming tools. You can access Homebrew via the terminal, (like all good things). Inspiration for this section comes from Kenneth Reitz’s excellent Python guide.
Install Homebrew by pasting this command into your terminal and then hitting “enter.”
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
It will ask for your password, so type that in and hit “enter” again. Now, paste this line to test Homebrew.
This will test your Homebrew setup, and any tools you’ve installed to make sure they’re working properly. If they are, Homebrew tell you
Your system is ready to brew.
If anything isn’t working properly, follow their instructions to get things working correctly.
Note: If there are two lines inside any of the code blocks in this article, paste them separately and hit enter after each of them.
Next you’ll need to go in and edit
~/.bash_profile to ensures you can use what you’ve just downloaded.
bash_profile acts like a configuration file for your terminal.
Note: There are many editors available on your computer. You can use a pretty graphical editor like SublimeText2 or you can use one built-in to your terminal, like
nano. We’ll be using
nano for this tutorial just to keep things simple.
bash_profile with the following command.
Then copy and paste this line of code at the very top. This lets Homebrew handle updating and maintaining the code we’ll be installing.
Once you’ve added the line of code, you can save the file by typing control + O. Doing so lets you adjust the file name. Just leave it as is, then hit enter to save. Hit control + X to exit. You’ll find yourself back at the command line and needing to update your terminal session like so. Copy and paste the next line of code into your terminal and hit enter.
You’ll only need to source the
bash_profile since we’re editing the file right now. It’s the equivalent of quitting your terminal application and opening it up again, but
source lets you soldier forward and setup Python.
Chapter 2: Install Python 2 and virtualenv
macOS comes with a system version of Python, and for a long time, we used this version. However, modifying the system Python is inadvisable; user alterations or installations may cause core macOS components to break, and macOS system updates may cause user projects to break.
Thus, install the latest stable homebrewed version of Python. Most of our team’s projects use Python 2, so we’ll install that version instead of Python 3; following from this, we’ll use the
pip2 commands to invoke those tools in the terminal.
brew install python2
You may have to update your
PATH environment variable to tell your system to prefer the version of Python you just installed over the system version. The output of
brew install python2 should include some text like this:
This formula installs a python2 executable to /usr/local/bin. If you wish to have this formula’s python executable in your PATH then add the following to ~/.bash_profile:
I updated my path in
~/.bash_profile so that
/usr/local/opt/python/libexec/bin was at the beginning of the path list and then made my current shell use the updated path by running
pip2 is like Homebrew: it’s sort of an app store but for Python code.
Next, we’ll install
virtualenvwrapper. These tools help us isolate Python projects into their own little sandboxes, keeping your installed software neat and tidy.
pip2 install virtualenv virtualenvwrapper
virtualenv creates the actual environment that you’ll be using, while
virtualwrapper makes the interface to these virtual environments even simpler.
~/.bash_profile file again,
and add this line below the line you just added:
Save and exit out of
nano using control + O, enter, and then control + X.
Sanity Check: Double check your
~/.bash_profile file, and make sure you’ve properly saved your
It should look like this:
export PATH=/usr/local/bin:$PATH source /usr/local/bin/virtualenvwrapper_lazy.sh
less, press “Q”.
To check if
virtualenv is properly working, you can create a virtual environment to test it by running:
After making a few python executables, this should create a new virtual environment for you. If you’re in a virtual environment, you should see
(my_virtual_env_name) inserted before each line in the terminal. Then, to exit out of the virtual environment, run:
This will deactivate but not delete the test virtual environment. To delete the virtual environment, use
A note about virtual environments
April 18, 2016: We recently learned that if you installed
virtualenv before installing the Homebrew version of Python (and possibly even if you installed Python first), the virtual environments you create will use the macOS system version of Python. This is not cool because that version of Python is compiled without key features and libraries.
To ensure you always are using your Homebrewed Python, always specify the
--python flag when creating a virtual environment:
mkvirtualenv --python "$(which python2)" my_virtual_env_name
This will make a virtual environment with the active Python version on your
Chapter 3: Set up Node and install LESS
nvm, which lets you easily upgrade and switch between Node versions.
nvm with this line. It will ask you to update your Bash config, or close and re-open your terminal after it completes.
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.2/install.sh | bash
Once that’s done, you can actually use
nvm to install Node:
nvm install stable
You may want to install a couple of helper libraries for working with our projects. The
-g flag means that they’re globally installed, so that they become available as command-line executables:
npm install -g less grunt-cli grunt-init prettier
After that, you can treat yourself to a cup of coffee because you now have the basic tools for working like the NPR Visuals team. Next up we’ll be getting into the nitty gritty of working with the template, including things like GitHub and Amazon Web Services.
Chapter 4: Configure git
Set up SSH for Github
Github has written a great guide for setting up SSH authentication for Github. You will want to do this so Github knows about your computer and will allow you to push to repositories you have access to.
Read that tutorial here. Start at “Step 1: Check for SSH keys”.
Configure the default identity
It’s nice to have your name and email show up correctly in the commit log. To make sure this information is correct, run:
git config --global user.email "$YOUR_EMAIL@npr.org" git config --global user.name "$YOUR_NAME"
You can also use the GitHub Desktop app to manage your repositories, since it will make it easier to check diffs or browse through repo history.
Optional: set up bash completion
I like to be able to tab-complete my branch names when doing
git checkout. The easiest way I found to do this is to install Homebrew’s git instead of the default macOS one, as well as the bash completion package:
brew install git bash-completion
Then add a line like this to your
[ -f /usr/local/etc/bash_completion ] && . /usr/local/etc/bash_completion
Appendix 1: Postgres and PostGIS
We occasionally make maps and analyze geographic information, so that requires some specialized tools. This appendix will show you how to install the Postgres database server and the PostGIS geography stack — which includes several pieces of software for reading and manipulating geographic data.
While you can install Postgres using Homebrew, the easiest way to manage Postgres on your Mac is with Postgres.app. This application provides a very basic GUI around the database, and sits in your menu bar to show whether the database is running. It also comes with useful extensions baked in, including PostGIS.
Appendix 2: The Terminal
Since you’re going to be working from the command line a lot, it’s worth investing time to make your terminal something that’s a little more easy on the eyes.
Download iTerm2. The built-in terminal application which comes with your Mac is fine, but iTerm2 is slicker and more configurable. One of the better features is splitting your terminal into different horizontal and vertical panes: one for an active pane, another for any files you might want to have open, and a third for a local server.
Solarized is a set of nice, readable colors. Unzip the
Now, inside iTerm2 go to iTerm > Preferences > Profiles and select “Default.” Choose “Colors” and find the “Color Presets…” button in the lower-right-hand corner of the window. Select “Import” and navigate to
solarized/iterm2-colors-solarized/ and double-click on
Solarized Dark.itermcolors. After it’s been imported, you can find “Solarized Dark” on the “Load Presets” list. Click and select “Solarized Dark” to change the colors appropriately.
See? Much nicer.
Appendix 3: The Text Editor
Since your code is stored entirely as text files on your computer, you’ll want a nice text editor. Our instructions showed you how to use
nano, a text editor that you’ll find on almost every computer. However, there are at least two others that the team uses. Text editors are like the Microsoft Word of the programming world, except they come packed with all kinds of handy dandy features to make writing code a cinch.
While I prefer vim (see below) as my editor of choice, many people prefer an editor that is less dependent on memorizing keystrokes and has a user interface that you can interact with using your mouse or trackpad. If this is you, Atom is a good choice because it’s free and intuitive to use with its defaults, yet highly customizable.
I have this installed on my system in case I’m pairing with someone who’s not familiar with vim.
Sublime Text is another GUI-based editor with a nice interface and some customizations available. You’ll likely want to learn some keyboard shortcuts to make yourself more efficient. You can also prettify it with the Flatland theme.
Personally, I prefer vim — a terminal based editor that requires you to type rather than point-and-click to work on files. I learned this editor at one of my first jobs when the sysadmin pointed out that it was good to know vi (vim stands for “vi improved”) because it was likely to be available on any Linux server to which you may find yourself connecting. There’s a lot of little keyboard shortcuts you’ll need to get comfy with before you can just dive-in. Here’s a resource to become more acquainted with vim: Vim Tips Wiki.
A version of vim is already on your computer, but I prefer to install it using Homebrew to get a more up-to-date version. You can do this by running
brew install vim
Some team members use Janus, a vim distribution that comes with a number of useful plugins preinstalled and with some useful configuration presets. For better or for worse, I’ve built up a vim configuration over the years, which you can find here. It uses Vundle to manage installing plugin packages. Pathogen is another popular option and Vim 8 has built-in package management support.
Note: In your terminal, type in
vim to begin using the editor.
Configure your default editor for git
Regardless of which editor you prefer, you should set the default editor used by git. This way, if you run
git commit without the
-m option, an editor will be opened so you can type a descriptive, nicely-formatted commit message.
You can do this with this command:
git config --global core.editor $PATH\_TO\_EDITOR
I used the
which command to easily find the path to
git config --global core.editor $(which vim)
And with that you now have a sweet hackintosh. Happy hacking, and if you haven’t setup a Github account, you can try out your new tools and play with some of our code. Github provides a thorough walkthrough to get you setup and working on some open sourced projects.