On 21/07/2011 6:32 PM, Glenn Linderman wrote: > On 7/20/2011 11:35 PM, Mark Hammond wrote: >> * If the command starts with the definition of a customized command >> followed by a space character, the customized command will be used. >> See below for a description of customized commands. > >> Then a shebang line of '#! vpython' in a script named 'doit.py' will >> result in the launcher using the command-line 'c:\bin\vpython.exe -foo >> doit.py' > > Shouldn't the second paragraph include a space before the 2nd ' ? In > other words, the command as quoted does not show a "customized command > followed by a space character" as the definition requires. I don't know > why the space character is required, or maybe "white space" was meant, > so that the line terminating newline character qualifies also to delimit > the customized command? Yes, thanks for pointing that out - I've pushed a new version of the PEP with that paragraph reading as: """ If the command starts with the definition of a customized command followed by a whitespace character (including a newline), the customized command will be used. See below for a description of customized commands. """ Thanks, Mark > > > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/skippy.hammond%40gmail.com
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4