Guido van Rossum wrote: > There's a cost to __future__ imports > too. The current proposal is a pretty clever hack -- and we've done > similar hacks in the past There's a benefit to having a __future__ import beyond avoiding hackery: by turning on the __future__ you can find out what will break when they become real keywords. But I suppose that could be achieved by having both the hack *and* the __future__ import available. -- Greg
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