-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
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
On Oct 8, 2014, at 3:36 PM, Wes Turner wes.tur...@gmail.com wrote:
On Oct 8, 2014 7:20 AM, Donald Stufft don...@stufft.io
mailto:don...@stufft.io wrote:
On Oct 8, 2014, at 6:16 AM, Christian Tismer tis...@stackless.com
mailto:tis...@stackless.com wrote:
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08.10.14 14:20, Donald Stufft wrote:
On Oct 8, 2014, at 6:16 AM, Christian Tismer tis...@stackless.com
wrote:
...
So is there anything officially preferred, and should that go into pep 8?
Some editors can use shebang lines to control
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
On Oct 08, 2014, at 08:20 AM, Donald Stufft wrote:
Some editors can use shebang lines to control syntax highlighting or linting
(mine for example will lint different for python2 vs python3 shebangs).
Some editors can also use `# -*- foo -*-` comments to set up editing modes and
there are other
