Yelp/mrjob — Issue #251: bootstrap cmds run after bootstrap python modules
Author: Roguelazer
Created: 2011-11-02 05:14:07+00:00
State: open
Labels: Feature

Let's say, just hypothetically, that you wanted to use a python module on EMR which required a bunch of system modules to build. Say, a library like M2Crypto, which depends on libssl and swig. So you go about your business of adding a bootstrap_cmd of `sudo apt-get install libssl-dev swig`, and adding a boostrap_python_module of `module.tar.gz`. All set, right?

**wrong**

mrjob apparently runs bootstrap cmds _after_ running the python module builds. Which is, of course, backwards for these purposes.

I imagine that existing configs would be broken by reversing this (I could imagine a case where you want your bootstrap_cmd to use a python module that you just built), so maybe it would best to have an `early_bootstrap_cmd` option? Anyhow, just another annoyance on the road of mrjob.