reonokiy/swh-lister
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs/tutorials: Format sentences

Browse source
This commit is contained in:
Antoine R. Dumont (@ardumont) 2018-06-26 10:48:12 +02:00
parent 4b351321d8
commit d9a25865a2
No known key found for this signature in database
GPG key ID: 52E2E9840D10C3B8
1 changed files with 8 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/tutorial.rst
View file

@ -268,13 +268,14 @@ We can also see that there are a few differences:
* GitHub sends the next URL as part of the response header, while BitBucket
sends it in the response body.
* GitHub differentiates API versions with a request header (our HTTP transport
mix-in will automatically use any headers provided by an optional
request_headers method that we implement here), while BitBucket has it as part
of their base service URL. BitBucket uses the IETF standard HTTP 429 response
code for their rate limit notifications (the HTTP transport mix-in
automatically handles that), while GitHub uses their own custom response
headers that need special treatment.
* GitHub differentiates API versions with a request header (our HTTP
transport mix-in will automatically use any headers provided by an
optional request_headers method that we implement here), while
BitBucket has it as part of their base service URL. BitBucket uses
the IETF standard HTTP 429 response code for their rate limit
notifications (the HTTP transport mix-in automatically handles
that), while GitHub uses their own custom response headers that need
special treatment.
* But look at them! 58 lines of Python code, combined, to absorb all
repositories from two of the largest and most influential source code hosting