Docs: Clarify that -I is not a security boundary#150790
Docs: Clarify that -I is not a security boundary#150790StanFromIreland wants to merge 2 commits into
-I is not a security boundary#150790Conversation
|
|
||
| .. option:: -E | ||
|
|
||
| Ignore all ``PYTHON*`` environment variables, e.g. |
There was a problem hiding this comment.
Should I also add the note here, I was split?
There was a problem hiding this comment.
I don't think it is necessary since the section also includes the "see also the -I option", but it is up to you and the core team
There was a problem hiding this comment.
I'd rather see a more positive description of what this is for - e.g. "this is useful for running commands that should not take into account the user's current environment settings, but does not necessarily mean that the current environment will have no effect." Once that's in, maybe it'll make sense to also say what it's not, but I don't think it's real helpful to jump straight to what it isn't without saying what it is.
Documentation build overview
|
Co-authored-by: Bartosz Sławecki <bartosz@ilikepython.com>
|
@zooba, any thoughts here? |
No description provided.