Commonly-used names in the Python standard library
Chris Angelico
rosuav at gmail.com
Thu Feb 20 07:19:25 EST 2014
More information about the Python-list mailing list
Thu Feb 20 07:19:25 EST 2014
- Previous message (by thread): Commonly-used names in the Python standard library
- Next message (by thread): Commonly-used names in the Python standard library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Feb 20, 2014 at 11:09 PM, Marko Rauhamaa <marko at pacujo.net> wrote: > How about blocking the introduction of new keywords for ever except if > you specify: > > from __py35__ import syntax > > Eventually, every Python module would likely begin with a statement like > that, and it would document the assumption more clearly than __future__. It's more self-documenting with the __future__ directive, because it says *what* syntax you're importing from the future. And at some point, the new keywords must just become standard. There's no point polluting every Python script forever with these directives, and no point maintaining two branches of code in the interpreter. ChrisA
- Previous message (by thread): Commonly-used names in the Python standard library
- Next message (by thread): Commonly-used names in the Python standard library
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list