$_{-I}$option can be used to run the script in isolated mode where$_{sys.path}$ contains neither the script’s direc- tory nor the user’s site-packages directory. All PYTHON* environment variables are ignored, too. 

Raises an auditing event$_{cpython.run_file}$ with argument$_{filename}$ . 

See also: 

runpy.run_path() Equivalent functionality directly available to Python code 

If no interface option is given,$_{-i}$is implied,$_{sys.argv[0]}$ is an empty string ($_{""}$ ) and the current directory will be added to the start of sys.path . Also, tab-completion and history editing is automatically enabled, if available on your platform (see rlcompleter-config). 

See also: 

tut-invoking 

Changed in version 3.4: Automatic enabling of tab-completion and history editing. 

## 1.1.2 Generic options 

## -? 

## -h 

## --help 

Print a short description of all command line options. 

## -V 

## --version 

Print the Python version number and exit. Example output could be: 

Python 3.8.0b2+ 

When given twice, print more information about the build, like: 

Python 3.8.0b2+ (3.8:0c076caaa8, Apr 20 2019, 21:55:00) [GCC 6.2.0 20161005] 

New in version 3.6: The$_{-VV}$option. 

## 1.1.3 Miscellaneous options 

## -b 

Issue a warning when comparing$_{bytes}$or$_{bytearray}$with$_{str}$or$_{bytes}$with$_{int}$. Issue an error when the option is given twice ($_{-bb}$ ). 

Changed in version 3.5: Affects comparisons of$_{bytes}$with$_{int}$. 

## -B 

If given, Python won’t try to write $_{.pyc}$files on the import of source modules. See also PYTHONDONTWRITEBYTECODE . 

## --check-hash-based-pycs default|always|never 

Control the validation behavior of hash-based$_{.pyc}$files. See pyc-invalidation. When set to$_{default}$ , checked and unchecked hash-based bytecode cache files are validated according to their default semantics. When set to$_{always}$ , all hash-based$_{.pyc}$ files, whether checked or unchecked, are validated against their corresponding source file. When set to$_{never}$, hash-based$_{.pyc}$ files are not validated against their corre- sponding source files. 

The semantics of timestamp-based$_{.pyc}$ files are unaffected by this option. 

