Repository navigation
Missing isolated (-I) flag in sys.flags table #79082
Description
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 2018-10-22.22:01:57.156>
created_at = <Date 2018-10-05.04:16:39.968>
labels = ['3.7', '3.8', 'docs']
title = 'Missing isolated (-I) flag in sys.flags table'
updated_at = <Date 2018-10-22.22:01:57.155>
user = 'https://github.com/danishprakash'bugs.python.org fields:
activity = <Date 2018-10-22.22:01:57.155>
actor = 'ned.deily'
assignee = 'docs@python'
closed = True
closed_date = <Date 2018-10-22.22:01:57.156>
closer = 'ned.deily'
components = ['Documentation']
creation = <Date 2018-10-05.04:16:39.968>
creator = 'danishprakash'
dependencies = []
files = []
hgrepos = []
issue_num = 34901
keywords = ['patch']
message_count = 9.0
messages = ['327103', '327107', '327111', '327273', '327282', '327297', '327909', '328276', '328277']
nosy_count = 6.0
nosy_names = ['terry.reedy', 'ned.deily', 'docs@python', 'miss-islington', 'xtreak', 'danishprakash']
pr_nums = ['9708', '9749', '9755']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue34901'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
Activity
tirkarthi commentedon Oct 5, 2018
Thanks for the PR @danishprakash .
-Iwas added as part of 3.4 with commit ad73a9c and not backported to 2.7 . Also 3.4 and 3.5 branches are in security fixes mode. So I am removing 2.7, 3.4 and 3.5 .danishprakash commentedon Oct 5, 2018
thank you for for making the corrections, however, what's with a version being in security fixes mode? I would like to read more about that.
tirkarthi commentedon Oct 5, 2018
Every release has a PEP associated with it from 3.6 and above that says about the lifespan of the release with bug fix releases and the time where it enters security fixes only mode. Now 3.4 and 3.5 are in security fixes mode where only security updates for the most part are accepted and the changes are pulled in by the release manager to the respective branches. Also there will be no binary releases and only source releases for security only branches.
Python 3.5.6 security announcement : https://www.python.org/downloads/release/python-356/
Python 3.8 release lifespan : https://www.python.org/dev/peps/pep-0569/#lifespan
So I have removed 3.4 and 3.5 but it's up to the reviewer to decide if this needs to be backported or not to those branches. I hope I am correct on the above.
danishprakash commentedon Oct 7, 2018
Thanks for the concise explanation, that makes sense.
Is there any particular reason as to why this happens? IS it just to make it easier for the team to focus on the development of current versions or something else?
miss-islington commentedon Oct 7, 2018
New changeset c59e75c by Miss Islington (bot) in branch '3.7':
bpo-34901: add isolated (-I) flag to sys.flags (GH-9708)
c59e75c
tirkarthi commentedon Oct 7, 2018
Sorry, I don't have a better explanation over the workflow.
terryjreedy commentedon Oct 17, 2018
In spite of what is said above, PR 9708 was merged before the auto-backport.
ned-deily commentedon Oct 22, 2018
New changeset da7d7d0 by Ned Deily (danishprakash) in branch '3.6':
[3.6] bpo-34901: add -I flag to sys.flags (GH-9755)
da7d7d0
ned-deily commentedon Oct 22, 2018
Thanks, Danish and everyone else!