On 30 January 2017 at 19:05, Brett Cannon <br...@python.org> wrote: > On Sun, 29 Jan 2017 at 16:39 Craig Rodrigues <rodr...@freebsd.org> wrote: >> I'm OK with either approach. Leaving things the way they are in Python 3 >> is no good, IMHO. > > My vote is it be a SyntaxError since you're not getting what you expect from > the syntax.
I'd agree that's a sensible place for us to end up, as any code relying on the current behaviour is really too clever to be maintainable. In terms of getting there, we'll likely want: - SyntaxWarning or DeprecationWarning in 3.7 - Py3k warning in 2.7.x - SyntaxError in 3.8 Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
