Repository navigation
Ensure PEP 663 changes are reverted from 3.11 #91041
Description
| BPO | 46885 |
|---|---|
| Nosy | @Yhg1s, @ethanfurman, @pablogsal |
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 = 'https://github.com/ethanfurman'
closed_at = None
created_at = <Date 2022-02-28.18:53:32.435>
labels = ['3.11']
title = 'Ensure PEP 663 changes are reverted from 3.11'
updated_at = <Date 2022-03-02.16:51:17.659>
user = 'https://github.com/pablogsal'bugs.python.org fields:
activity = <Date 2022-03-02.16:51:17.659>
actor = 'ethan.furman'
assignee = 'ethan.furman'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2022-02-28.18:53:32.435>
creator = 'pablogsal'
dependencies = []
files = []
hgrepos = []
issue_num = 46885
keywords = []
message_count = 3.0
messages = ['414214', '414215', '414217']
nosy_count = 3.0
nosy_names = ['twouters', 'ethan.furman', 'pablogsal']
pr_nums = []
priority = 'high'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue46885'
versions = ['Python 3.11']
Activity
pablogsal commentedon Feb 28, 2022
As PEP-663 python/steering-council#76 was rejected, we need to ensure that the changes made in 3.11 (see python/steering-council#76 (comment)) are rejected.
I am marking this as a release blocker so we don't forget.
pablogsal commentedon Feb 28, 2022
Apologies, I meant "we need to ensure that the changes made in 3.11 are **reverted**.
ethanfurman commentedon Feb 28, 2022
This has been taken care of in bpo-40066.