This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jim Fasarakis-Hilliard
Recipients Jim Fasarakis-Hilliard, Mariatta, docs@python, marco.buttu, rhettinger
Date 2017-01-28.16:55:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Indeed, this does create an issue. 

The last sentence in the documentation actually specifies where the encoding comment can be but doesn't strictly specify it can be on the second line if and only if preceded by `#!`.

I'm thinking the last sentence should contain the additional change, that is, change it from :

    The special encoding comment must be in the first or second line within the file.


    The special encoding comment must be in the first line, or, if the first line is used to create an executable Python script, the second line within the file.

linking to ( accordingly. 

Let's see what Mariatta says about these proposals. Thanks for noticing.
Date User Action Args
2017-01-28 16:55:13Jim Fasarakis-Hilliardsetrecipients: + Jim Fasarakis-Hilliard, rhettinger, docs@python, marco.buttu, Mariatta
2017-01-28 16:55:13Jim Fasarakis-Hilliardsetmessageid: <>
2017-01-28 16:55:13Jim Fasarakis-Hilliardlinkissue29381 messages
2017-01-28 16:55:12Jim Fasarakis-Hilliardcreate