:\codewhat py unable to create process using '/bin/python " :\code\what pyc:\codepy what py unable to create process using '/bin/python what pyc:\codepy - what py technicallythe launcher recognizes unix-style #lines at the top of script files that follow one of the following four patterns#!/usr/bin/env python#!/usr/bin/python#!/usr/local/bin/python#!pythonany #line that does not take one of these recognized and parseable forms is assumed to be fully specified command line to start process to run the filewhich is passed to windows as isand generates the error message we saw previously if it is not valid windows command (the launcher also supports "customizedcommand expansions via its configuration fileswhich are attempted before passing unrecognized commands on to windowsbut we'll gloss over these here in recognizable #linesdirectory paths are coded per unix conventionfor portability to that platform the part at the end of the four preceding recognized patterns denotes an optional python version numberin one of three formspartial ( python to run the version installed with the highest minor release number among those with the major release number given full ( python to run that specific version onlyoptionally suffixed by - to prefer -bit version ( pythonomitted ( pythonto run the launcher' default versionwhich is unless changed ( by setting the py_python environment variable to )another pitfall described ahead files with no #line at all behave the same as those that name just generic python-the aforementioned omitted case--and are influenced by py_python default settings the first casepartialsmay also be affected by version-specific environment settings ( set py_python to to select for python and set py_python to to pick for python we'll revisit defaults later in this tutorial firstthoughnote that anything after the part in #line' format is assumed to be command-line arguments to python itself ( program python exe)unless you also windows launcher tutorial