Forbid creating of stream objects outside of asyncio

[asvetlov]

BPO	36806
Nosy	@asvetlov, @1st1
PRs	bpo-36806: Forbid stream objects creation outside of asyncio #13101

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2019-05-07.02:54:08.635>
created_at = <Date 2019-05-05.19:15:37.730>
labels = ['3.8', 'expert-asyncio']
title = 'Forbid creating of stream objects outside of asyncio'
updated_at = <Date 2019-05-07.02:54:08.632>
user = 'https://github.com/asvetlov'

bugs.python.org fields:

activity = <Date 2019-05-07.02:54:08.632>
actor = 'asvetlov'
assignee = 'none'
closed = True
closed_date = <Date 2019-05-07.02:54:08.635>
closer = 'asvetlov'
components = ['asyncio']
creation = <Date 2019-05-05.19:15:37.730>
creator = 'asvetlov'
dependencies = []
files = []
hgrepos = []
issue_num = 36806
keywords = ['patch']
message_count = 1.0
messages = ['341472']
nosy_count = 2.0
nosy_names = ['asvetlov', 'yselivanov']
pr_nums = ['13101']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue36806'
versions = ['Python 3.8']

[asvetlov]

They were intended to be used by asyncio factories like open_connection from the very beginning but internals was leaked into asyncio top-level namespace.

The idea is:

1. provide _asyncio_internal keyword-only parameter to leaked classes constructor
2. have it False by default
3. Use _asyncio_internal=True when called from asyncio code.
4. Raise DeprecationWarning if _asyncio_internal is False