<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 8, 2014, at 3:36 PM, Wes Turner <<a href="mailto:wes.turner@gmail.com" class="">wes.turner@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p dir="ltr" class=""><br class="">
On Oct 8, 2014 7:20 AM, "Donald Stufft" <<a href="mailto:donald@stufft.io" class="">donald@stufft.io</a>> wrote:<br class="">
><br class="">
><br class="">
> > On Oct 8, 2014, at 6:16 AM, Christian Tismer <<a href="mailto:tismer@stackless.com" class="">tismer@stackless.com</a>> wrote:<br class="">
> ><br class="">
> ><br class="">
> > -----BEGIN PGP SIGNED MESSAGE-----<br class="">
> > Hash: SHA512<br class="">
> ><br class="">
> > Howdy,<br class="">
> ><br class="">
> > this question is a bit about general policy which is not yet<br class="">
> > covered in the python recommendations:<br class="">
> ><br class="">
> > I see projects which do check-ins like "get rid of shebang lines"<br class="">
> > and they remove those lines from non-script sources.<br class="">
> ><br class="">
> > It is not always clear to me what to do, so I tend to leave those<br class="">
> > lines in per default, in order not to waste time thinking about it,<br class="">
> > but well, today I was confronted with that.<br class="">
> ><br class="">
> > Digging a bit deeper shows the following:<br class="">
> ><br class="">
> > python docs:<br class="">
> > No mention of shebang, but for Windows.<br class="">
> > <a href="https://docs.python.org/3/search.html?q=shebang&check_keywords=yes&area=default" class="">https://docs.python.org/3/search.html?q=shebang&check_keywords=yes&area=default</a><br class="">
> > <a href="https://docs.python.org/3/using/windows.html?highlight=shebang" class="">https://docs.python.org/3/using/windows.html?highlight=shebang</a><br class="">
> ><br class="">
> > Google's python style guide also says when a shebang is needed, but<br class="">
> > does not forbid it.<br class="">
> ><br class="">
> > Pep 394 explains how to use shebang, but still nothing about not using it.<br class="">
> > <a href="http://legacy.python.org/dev/peps/pep-0394/" class="">http://legacy.python.org/dev/peps/pep-0394/</a><br class="">
> ><br class="">
> > So is there anything officially preferred, and should that go into pep 8?<br class="">
><br class="">
> Some editors can use shebang lines to control syntax highlighting or linting<br class="">
> (mine for example will lint different for python2 vs python3 shebangs).</p><p dir="ltr" class="">Does it support shebang lines like:</p><p dir="ltr" class="">#!/usr/bin/env python</p><p dir="ltr" class="">?</p>
</div></blockquote></div><div class="">Sure. Though it doesn’t resolve it to determine what that would actually execute,</div><div class="">it just uses the name of the python in the shebang as heuristics.</div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">---</div><div class="">Donald Stufft</div><div class="">PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA</div></div></div>
</div>
<br class=""></body></html>