[issue34901] Missing isolated (-I) flag in sys.flags table

Ned Deily added the comment: Thanks, Danish and everyone else! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue34901] Missing isolated (-I) flag in sys.flags table

Ned Deily added the comment: New changeset da7d7d0ccc2e7cab62080e146cab027f2aa6fd03 by Ned Deily (danishprakash) in branch '3.6': [3.6] bpo-34901: add -I flag to sys.flags (GH-9755) https://github.com/python/cpython/commit/da7d7d0ccc2e7cab62080e146cab027f2aa6fd03 -- nosy:

[issue34901] Missing isolated (-I) flag in sys.flags table

Change by Danish Prakash : -- pull_requests: +9283 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34901] Missing isolated (-I) flag in sys.flags table

Terry J. Reedy added the comment: In spite of what is said above, PR 9708 was merged before the auto-backport. -- nosy: +terry.reedy ___ Python tracker ___

[issue34901] Missing isolated (-I) flag in sys.flags table

Karthikeyan Singaravelan added the comment: >> Also there will be no binary releases and only source releases for security >> only branches. > 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

[issue34901] Missing isolated (-I) flag in sys.flags table

miss-islington added the comment: New changeset c59e75ccf0ea8d882738214e0385f41eed51e3c7 by Miss Islington (bot) in branch '3.7': bpo-34901: add isolated (-I) flag to sys.flags (GH-9708) https://github.com/python/cpython/commit/c59e75ccf0ea8d882738214e0385f41eed51e3c7 -- nosy:

[issue34901] Missing isolated (-I) flag in sys.flags table

Change by miss-islington : -- pull_requests: +9135 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34901] Missing isolated (-I) flag in sys.flags table

Danish Prakash added the comment: Thanks for the concise explanation, that makes sense. > Also there will be no binary releases and only source releases for security > only branches. Is there any particular reason as to why this happens? IS it just to make it easier for the team to focus

[issue34901] Missing isolated (-I) flag in sys.flags table

Karthikeyan Singaravelan added the comment: 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

[issue34901] Missing isolated (-I) flag in sys.flags table

Danish Prakash added the comment: 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. -- ___ Python tracker

[issue34901] Missing isolated (-I) flag in sys.flags table

New submission from Karthikeyan Singaravelan : Thanks for the PR @danishprakash . `-I` was added as part of 3.4 with commit ad73a9cf977 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 . -- nosy: +xtreak versions:

[issue34901] Missing isolated (-I) flag in sys.flags table

Change by Roundup Robot : -- keywords: +patch pull_requests: +9093 stage: -> patch review ___ Python tracker ___ ___

[issue34901] Missing isolated (-I) flag in sys.flags table

Change by Danish Prakash : -- assignee: docs@python components: Documentation nosy: danishprakash, docs@python priority: normal severity: normal status: open title: Missing isolated (-I) flag in sys.flags table versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7,