Fix docstrings, pep8, pep257, and add param doc for in exceptions.py

[terryjbates]

No description provided.

[codecov-io]

Current coverage is 100% (diff: 100%)

Merging #786 into master will not change coverage

@@           master   #786   diff @@
====================================
  Files          14     15     +1   
  Lines         599    605     +6   
  Methods         0      0          
  Messages        0      0          
  Branches        0      0          
====================================
+ Hits          599    605     +6   
  Misses          0      0          
  Partials        0      0          

Powered by Codecov. Last update 5db20b2...8be6e8a

[hackebrot]

Can you please remove the shebang? Thank you! 🙇

[terryjbates]

@hackebrot Appears that removing the shebang line causes Travis CI to fail, due to an InvocationError

https://travis-ci.org/audreyr/cookiecutter/jobs/152247749

A bit mysterious. How shall we proceed?

[michaeljoseph]

@terryjbates the test failure looks unrelated to your change.

And @hackebrot has already raised an issue for the underlying problem: pytest-dev/pytest-mock#59

I guess we should pin pytest-mock for now.

[michaeljoseph]

@terryjbates rebasing on master to get 2d0affe should fix this failure now.

[terryjbates]

Mkay...not sure if I have horked this up or not, so let me know if I have! Tried the following:

1. On local master branch executed git fetch upstream and git merge upstream/master.
2. Changed branches to the topic branch of tbates-pep257-742-exceptions.
3. Did git pull.
4. Did git rebase -i master melded one two commits that were there into one.
5. git status indicated I had 10 and 2 commits in local and remote branch respectively.
6. Did a git pull --rebase.
7. Did git push and the Travis CI and Appveyor workflows seemed to have kicked off here in this PR.

Travis CI still seemed unhappy initially, though I do see this passes locally when I run:

tox -e py36

And I can see commit ceb0e409 via git log on that same topic branch.

[hackebrot]

Hi @terryjbates! 👋

Not really sure what happened here.

Can you please try the following:

• git checkout master
• git fetch upstream
• git merge upstream/master
• git push origin

Now your master should be up-to-date both locally and your fork.

• git checkout tbates-pep257-742-exceptions
• git rebase master
• git log master..HEAD

You should see two commits, both from you.

[terryjbates]

Thanks @hackebrot! I'm giving your commands a shot now. Thanks for helping get through merge hell. Looking back, I suspect I may not have pushed my local master to the master on GitHub.