I can confirm that the Travis check is indeed now firing.  Here is what I got when I pushed an in-progress (i.e. not yet fully PEP8-ified) branch:

 
Tim Jenness, are there any additional steps that need to be taken to "turn on" branch protection?

Would you have time to give this a look?  As the ticket describes, the main goal here is to get all code in pipe_analysis conforming with PEP8/Rubin standards.  As I was making these fixes, I couldn't help but notice a number of inconsistencies and unrecommended practices largely in the module documentation, so I took the opportunity to do some homogenizing/standardizing.  I tried to keep the independent changes in the separate commits, but it is likely a few of the latter slipped in former. This is also not meant to be a fully thorough upgrade to the documentation, but does fix some of the more egregious precedents that had been set (and, unfortunately, were being subsequently followed). I also certainly do not expect a line-by-line review here, but if you see anything particularly offensive, please let me know!

Lauren MacArthur that looks fine. I've gone through the GitHub project so it now requires that travis check to pass before merging (of course old pull requests will not be able to be merged from now until they are rebased on this ticket).

Awesome...thanks, Tim!

Looks (very) good to me!

I made a bunch of comments on the PR, but they are all extremely minor - a lot, if not most, related to punctuation in comments. Feel free to ignore these, and in any case okay to merge!

Thank you on behalf of all of us who will be going through the pipe_analysis code in the future!

Thank you for the expedient yet thorough review!  I addressed all you comments on the PR, including adding the copyright preamble where it was missing (thanks for pointing that out!)  As you saw on Slack, I did my best to poke the bear on the default specification issue as stated in our Dev Guide (but it's not a battle I really want to take on given the push-back...there are clearly cases that I'm not familiar with where this may be bad advice).  Merged and done!