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 ezio.melotti
Recipients ezio.melotti, kermit666, mark.dickinson, serhiy.storchaka
Date 2013-01-10.15:29:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357831779.28.0.575634681694.issue16917@psf.upfronthosting.co.za>
In-reply-to
Content
> This would all be a bit simpler if an indent was obligatory after
> inserting a newline in the middle of a command.

This is not such a bad idea, but it is not backward-compatible and it would be inconsistent with how parentheses works in other situations.

Developers usually learn that they should look back at least till the previous line while investigating syntax errors.  Even in C (and similar languages) it's common that errors reported on one line are caused by e.g. a missing ';' on the previous line.
History
Date User Action Args
2013-01-10 15:29:40ezio.melottisetrecipients: + ezio.melotti, mark.dickinson, serhiy.storchaka, kermit666
2013-01-10 15:29:39ezio.melottisetmessageid: <1357831779.28.0.575634681694.issue16917@psf.upfronthosting.co.za>
2013-01-10 15:29:39ezio.melottilinkissue16917 messages
2013-01-10 15:29:37ezio.melotticreate