(Where did this subject come from???) > > Martin's hack falls short of doing the right thing in all cases: you > > can't have the first statement of your program be "directive = ..." > > or "directive(...)". > > If that is considered as a serious problem, I'll try to solve it with > an additional lookahead token: If the next token is a name, then it is > a directive. Wait. MAL seems to want two other changes: directive should be allowed (required???) before the module docstring, and it should support the syntax from his proto-PEP (directive key = value). But MAL and PaulP don't seem to agree on the semantics of this directive, and I haven't gotten a good answer why we can't do that with a magic comment. In the mean time, I've decided to enable the yield keyword with a future statement. In general I now prefer using future statements for enabling future features over the directive statement. So it's still unclear if we want a directive... --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4