I guess this is in the pip install step... I think I've said this before but I really want to just excise all references to using pip for development environments. We aren't running the production one with randomly compiled stuff off PyPI, we are using properly built packages. So we really need to be recommending the same thing for development environments. If only to avoid mess like this.

OK, @dcallagh - what do we do with this ticket then? Reframe it as "change the README to use instructions other than pip"?

• Do we recommend rpms?
• Do we recommend building a container?

I, for one, think using pip to install deps in a virtualenv is fine and wouldn't mind additional steps introducing swig and gcc, etc.

I personally prefer to just yum-builddep (or equivalent) and then run from the git checkout directly, no virtualenv. I do it in a development VM to avoid messing up my real workstation.

#79 would be my preference, but I remember others preferred to use virtualenv so we don't have to go with #79 necessarily.

Yeah, let's close this with #79.