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 .

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.

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.5 has now entered "security fixes only" mode, and as such the only changes since Python 3.5.4 are security fixes. Also, Python 3.5.6 has only been released in source code form; no more official binary installers will be produced.

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.

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 on the development of current versions or something else?

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

>> 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 or something else?

Sorry, I don't have a better explanation over the workflow.

In spite of what is said above, PR 9708 was merged before the auto-backport.

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

Thanks, Danish and everyone else!