On 19 July 2016 at 22:05, Rustom Mody <rustompmody@gmail.com> wrote:
A more practical solution would be to take the best of the python2 and python3 current approaches: "Invalid character XX in line YY" and just reveal nothing about what lexical category — like identifier — python thinks the char is coming in.
There's historically been relatively little work put into designing the error messages coming out of the lexer, so if it's a task you're interested in stepping up and taking on, you could probably find someone willing to review the patches. But if you perceive "Volunteers used their time as efficiently as possible whilst fully Unicode enabling the CPython compilation toolchain, since it was a dependency that needed to be addressed in order to permit other more interesting changes, rather than an inherently rewarding activity in its own right" as "wrongheaded", you may want to spend some time considering the differences between community-driven and customer-driven development. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia