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 kermit666
Recipients ezio.melotti, kermit666, mark.dickinson, serhiy.storchaka
Date 2013-01-11.13:03:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADg_27-W5Vjv_jzgR7D_uNgPyUu0aH652toqks=D9rGPaeuqXA@mail.gmail.com>
In-reply-to <1357831779.28.0.575634681694.issue16917@psf.upfronthosting.co.za>
Content
Yes, I see your point.

Well, for now I am voting for issue1634034 to get some sort of
resolution, as Serhiy mentioned, as it might help this scenario as
well.

Cheers!

On Thu, Jan 10, 2013 at 4:29 PM, Ezio Melotti <report@bugs.python.org> wrote:
>
> Ezio Melotti added the comment:
>
>> 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.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue16917>
> _______________________________________
History
Date User Action Args
2013-01-11 13:03:11kermit666setrecipients: + kermit666, mark.dickinson, ezio.melotti, serhiy.storchaka
2013-01-11 13:03:10kermit666linkissue16917 messages
2013-01-11 13:03:09kermit666create