Skip to content

/ peps

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Proposal: A Unified TLS API for Python #208

Merged
merged 1 commit into from Feb 13, 2017
Merged

Proposal: A Unified TLS API for Python #208

merged 1 commit into from Feb 13, 2017

Conversation

@Lukasa
Copy link
Contributor

@Lukasa Lukasa commented Feb 13, 2017

This is a formal request for a PEP number for a draft PEP I have been shopping around the Python community for a couple of months now: a unified TLS API for Python. This draft PEP has been discussed multiple times on the Python Security-SIG mailing list, and once on python-ideas. At this point, I'd like to get a proper PEP number before I submit the PEP for consideration to python-dev (per the procedure in PEP 1).

Once the PEP number is assigned I'll send the PEP to python-dev for discussion. It's quite possible that this PEP will end up being revised in the face of python-dev feedback.
@the-knights-who-say-ni
Copy link

@the-knights-who-say-ni the-knights-who-say-ni commented Feb 13, 2017

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 we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA. This is necessary for legal reasons before we can look at your contribution. Please follow these steps to help rectify the issue:

  1. If you don't have an account on b.p.o, please create one
  2. Make sure your GitHub username is listed in "Your Details" at b.p.o
  3. If you have not already done so, please sign the PSF contributor agreement
  4. If you just signed the CLA, please wait at least a day and then check "Your Details" on bugs.python.org to see if your account has been marked as having signed the CLA (the delay is due to a person having to manually check your signed CLA)
  5. Reply here saying you have completed the above steps

Thanks again to your contribution and we look forward to looking at it!
@Lukasa
Copy link
Contributor Author

@Lukasa Lukasa commented Feb 13, 2017

I had already signed the CLA, so I just had to add my GitHub username to my bugs.python.org profile, which I have now done.
@methane methane added CLA signed and removed CLA not signed labels Feb 13, 2017
@Rosuav
Copy link
Contributor

@Rosuav Rosuav commented Feb 13, 2017

PEP 542 is claimed by another PR, so you can grab 543. I don't think I can push changes to your PR branch, so you'll have to commit your own change renaming this and setting the header.
@Lukasa
Initial proposal of TLS ABC PEP.
Verified
This commit was signed with a verified signature.
Lukasa Cory Benfield
GPG key ID: 70FE17F8A643E15B Learn about signing commits
Loading status checks…
213db01
@Lukasa Lukasa force-pushed the Lukasa:final-proposal branch from def9a06 to 213db01 Feb 13, 2017
@Lukasa
Copy link
Contributor Author

@Lukasa Lukasa commented Feb 13, 2017

ACK, now named PEP 543.
@Rosuav
Copy link
Contributor

@Rosuav Rosuav commented Feb 13, 2017

LGTM!
@Lukasa
Copy link
Contributor Author

@Lukasa Lukasa commented Feb 13, 2017

🎉
@Rosuav Rosuav merged commit a5ed08e into python:master Feb 13, 2017
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
CLA signed
Projects
None yet
Milestone
No milestone
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
@Lukasa @the-knights-who-say-ni @Rosuav @methane