Skip to content

bpo-30160: Clarify intended usage of request handler stream#1300

Merged
bitdancer merged 1 commit intopython:masterfrom
bocoup:clarify-stream-usage
May 24, 2017
Merged

bpo-30160: Clarify intended usage of request handler stream#1300
bitdancer merged 1 commit intopython:masterfrom
bocoup:clarify-stream-usage

Conversation

@jugglinmike
Copy link
Copy Markdown
Contributor

Although the library does not enforce compliance with the HTTP protocol,
violations are not technically disallowed. Extend the stream's
description to avoid suggesting that intentional protocol violations are
not supported.

Although the library does not enforce compliance with the HTTP protocol,
violations are not technically disallowed. Extend the stream's
description to avoid suggesting that intentional protocol violations are
not supported.
@the-knights-who-say-ni
Copy link
Copy Markdown

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

Thanks again to your contribution and we look forward to looking at it!

@mention-bot
Copy link
Copy Markdown

@jugglinmike, thanks for your PR! By analyzing the history of the files in this pull request, we identified @bitdancer, @birkenfeld and @benjaminp to be potential reviewers.

@jugglinmike
Copy link
Copy Markdown
Contributor Author

I signed the CLA immediately prior to submitting this pull request, but I understand that it may take up to 24 hours for that to be processed. Will any further action be necessary from me to re-validate this pull request?

@bitdancer
Copy link
Copy Markdown
Member

Not from you, no.

@bitdancer
Copy link
Copy Markdown
Member

I haven't gotten myself set up to do backports yet, so it would be great if you could generate those PRs.

zware pushed a commit to zware/cpython that referenced this pull request May 24, 2017
The library does not enforce compliance with the HTTP protocol,
so violations are not technically disallowed. Extend the stream's
description to avoid suggesting that intentional protocol violations are
not supported.
(cherry picked from commit a083c8e)
zware pushed a commit to zware/cpython that referenced this pull request May 24, 2017
The library does not enforce compliance with the HTTP protocol,
so violations are not technically disallowed. Extend the stream's
description to avoid suggesting that intentional protocol violations are
not supported.
(cherry picked from commit a083c8e)
zware added a commit that referenced this pull request May 24, 2017
The library does not enforce compliance with the HTTP protocol,
so violations are not technically disallowed. Extend the stream's
description to avoid suggesting that intentional protocol violations are
not supported.
(cherry picked from commit a083c8e)
zware added a commit that referenced this pull request May 24, 2017
The library does not enforce compliance with the HTTP protocol,
so violations are not technically disallowed. Extend the stream's
description to avoid suggesting that intentional protocol violations are
not supported.
(cherry picked from commit a083c8e)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants