On Oct 8, 2014 7:20 AM, "Donald Stufft" <don...@stufft.io> wrote: > > > > On Oct 8, 2014, at 6:16 AM, Christian Tismer <tis...@stackless.com> wrote: > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > Howdy, > > > > this question is a bit about general policy which is not yet > > covered in the python recommendations: > > > > I see projects which do check-ins like "get rid of shebang lines" > > and they remove those lines from non-script sources. > > > > It is not always clear to me what to do, so I tend to leave those > > lines in per default, in order not to waste time thinking about it, > > but well, today I was confronted with that. > > > > Digging a bit deeper shows the following: > > > > python docs: > > No mention of shebang, but for Windows. > > https://docs.python.org/3/search.html?q=shebang&check_keywords=yes&area=default > > https://docs.python.org/3/using/windows.html?highlight=shebang > > > > Google's python style guide also says when a shebang is needed, but > > does not forbid it. > > > > Pep 394 explains how to use shebang, but still nothing about not using it. > > http://legacy.python.org/dev/peps/pep-0394/ > > > > So is there anything officially preferred, and should that go into pep 8? > > Some editors can use shebang lines to control syntax highlighting or linting > (mine for example will lint different for python2 vs python3 shebangs).
Does it support shebang lines like: #!/usr/bin/env python ?
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
