On Tue, Aug 11, 2015 at 5:08 PM, Cameron Simpson <cs at zip.com.au> wrote: > On 11Aug2015 18:07, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote: >> >> Cameron Simpson wrote: >>> >>> To illustrate, there's a consumer rights TV snow here with a segment >>> called "F.U. Tube", where members of the public describe ripoffs and other >>> product failures in video form. While a phonetic play on the name "YouTube", >>> the abbreviation also colloquially means just what you think it might. I can >>> just imagine reciting one of these new strings out loud... >> >> >> We could require it to be spelled "uf" unless "from __future__ >> import billy_connolly_as_FLUFL" is in effect. > > > That seems like a reasoned and measured response. Given the levels of profanity that are not disallowed in identifier names, I think blocking off a two-letter prefix is pretty pointless. It'd be different if the specification _required_ it (though even then, it's not that big a deal...), but merely permitting it? Not Python's fault. ChrisA
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