Adding a reference section with a new book and line continuation style guide.#119
Conversation
|
Hi, I am doing my first pull requests on Github, some things are not very clear to me, sorry if any mess occurs. For instance, it seems that I can't queue separate pull requests to you, so apparently my second request has been merged into this one, and its message is not accurate anymore. (Nor will be this one if you accept or drop the request in between.) |
|
I am a bit of the corner-case paranoid style: what happens if I add a new commit to this pullreq just one second before you click on "accept"? Will the new patch be sneakily added to the book? Or this individual commit we get back home? Aya. |
|
@guibog All changes that are pushed to the same branch will be merged as part of any existing pull request from that branch. In order to separate your changes in to separate pull requests it's standard practice to make a new branch for each pull request. Usually the workflow for unrelated changes is something like: |
|
@kisielk thanks for the tip. |
|
Thanks! |
Adding a reference section with a new book and line continuation style guide.
|
Great stuff. |
By the way Python in a Nutshell is my preferred book about Python, but still can be improved. I would love if the hitchhiker guide could beat it!
Edit: Oh, I can edit pull request title and main comment, nice, but err, well. So github added a commit to this pullreq. Sorry if I messed anythings.