[Python-Dev] PEP 492 quibble and request (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Thu Apr 30 02:59:13 CEST 2015
- Previous message (by thread): [Python-Dev] PEP 492 quibble and request
- Next message (by thread): [Python-Dev] PEP 492 quibble and request
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 30 April 2015 at 10:21, Ethan Furman <ethan at stoneleaf.us> wrote:
From the PEP:
Why not a future import
future imports are inconvenient and easy to forget to add. That is a horrible rationale for not using an import. By that logic we should have everything in built-ins. ;)
It is also makes things more painful than they need to be for syntax highlighters. 'as' went through the "not really a keyword" path, and it's a recipe for complexity in the code generation toolchain and general quirkiness as things behave in unexpected ways.
We have a defined process for introducing new keywords (i.e. future imports) and the PEP doesn't adequately make the case for why we shouldn't use it here.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] PEP 492 quibble and request
- Next message (by thread): [Python-Dev] PEP 492 quibble and request
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]