Message 197617 - Python tracker

➜

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	lemburg
Recipients	benjamin.peterson, ezio.melotti, lemburg, loewis, serhiy.storchaka, terry.reedy
Date	2013-09-13.17:31:11
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<52334BD9.9000904@egenix.com>
In-reply-to	<1379093068.14.0.758472928339.issue18960@psf.upfronthosting.co.za>

Content
On 13.09.2013 19:24, Terry J. Reedy wrote: > > Terry J. Reedy added the comment: > > I thought that that was the specification: the encoding comment should be the first line unless it has to be the second line to allow for an executable comment. Executing a non-comment first line twice is definitely contrary to the intent of the PEP. > > I have not read it recently ;-). > > When running that snippet from 3.3.2 Idle editor, 'first' is only printed once. I consider this to be correct and I would not want to change Idle to match the buggy behavior. Agreed. The PEP never intended to allow executable first lines in a Python code file.

On 13.09.2013 19:24, Terry J. Reedy wrote:
> 
> Terry J. Reedy added the comment:
> 
> I thought that that was the specification*: the encoding comment should be the first line unless it has to be the second line to allow for an executable comment. Executing a non-comment first line twice is definitely contrary to the intent of the PEP.
> 
> * I have not read it recently ;-).
> 
> When running that snippet from 3.3.2 Idle editor, 'first' is only printed once. I consider this to be correct and I would not want to change Idle to match the buggy behavior.

Agreed. The PEP never intended to allow executable first lines in
a Python code file.

History
Date	User	Action	Args
2013-09-13 17:31:11	lemburg	set	recipients: + lemburg, loewis, terry.reedy, benjamin.peterson, ezio.melotti, serhiy.storchaka
2013-09-13 17:31:11	lemburg	link	issue18960 messages
2013-09-13 17:31:11	lemburg	create