Skip to content

Conversation

@asvetlov
Copy link
Contributor

@asvetlov asvetlov commented Nov 18, 2017

Legacy SSL transports was not used starting from Python 3.5, let's drop never executed code.

https://bugs.python.org/issue32069

@asvetlov asvetlov requested a review from 1st1 as a code owner November 18, 2017 15:10
@asvetlov asvetlov changed the title Drop legacy SSL transport bpo-32069: Drop legacy SSL transport Nov 18, 2017

import asyncio
from asyncio import selectors
from asyncio import sslproto
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this new import?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was my mistake, dropped.

@asvetlov asvetlov merged commit 51d546a into python:master Nov 18, 2017
@miss-islington
Copy link
Contributor

Thanks @asvetlov for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6.
🐍🍒⛏🤖

@asvetlov asvetlov deleted the drop-wrap_socket branch November 18, 2017 16:54
@bedevere-bot
Copy link

GH-4453 is a backport of this pull request to the 3.6 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Nov 18, 2017
* Drop legacy SSL transport

* Drop unused import

* Fix Windows tests

* Drop never executed on Python 3.4+ code
(cherry picked from commit 51d546a)
@1st1
Copy link
Member

1st1 commented Nov 18, 2017

Hey, this must not be merged to 3.6

@asvetlov
Copy link
Contributor Author

asvetlov commented Nov 18, 2017

Why?
The code in 3.6 will still keep working, nobody will see the change!
If you strongly disagree I'll make a revert commit but please tell me why?
All changes are for dropping 3.4 only features.

@1st1
Copy link
Member

1st1 commented Nov 18, 2017

3.6 is in a bug fix mode. Removing any APIs does not match that, unless it’s a critical security issue.

Maybe someone is importing/using these APIs manually. Breaking their code (however wrong it is) in a bugfix release is not an option.

@asvetlov
Copy link
Contributor Author

I've got your point.
Closing #4453

@asvetlov
Copy link
Contributor Author

Thanks for pointing on the problem.

@1st1
Copy link
Member

1st1 commented Nov 18, 2017

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants