bpo-34901: add isolated (-I) flag to sys.flags

[danishprakash]

https://bugs.python.org/issue34901

[the-knights-who-say-ni]

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for your contribution, we look forward to reviewing it!

[ned-deily]

Thanks for the PR and the update!

[miss-islington]

Thanks @danishprakash for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7.
🐍🍒⛏🤖

[bedevere-bot]

GH-9749 is a backport of this pull request to the 3.7 branch.

[miss-islington]

Sorry, @danishprakash, I could not cleanly backport this to 3.6 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 656d52dbfde3223cd2a3525d652b6cccb02fa991 3.6

[ned-deily]

@danishprakash, if you have time and are so inclined, it would be nice if you could do a manual backport to 3.6.

[danishprakash]

@ned-deily definitely, I assume it requires me to cherry-pick the commit as mentioned above and then open a PR against the 3.6 branch, is that right?

[tirkarthi]

@danishprakash Yes, you can install cherry_picker from PyPI and run the command mentioned which will help you.

[ned-deily]

@danishprakash Yes, that's right. You can use follow the process here or just manually use the git cherry-pick command.

[bedevere-bot]

GH-9755 is a backport of this pull request to the 3.6 branch.