On Sat, Feb 01, 2003 at 07:45:30PM +0100, Alex Martelli wrote: > On Saturday 01 February 2003 07:33 pm, Guido van Rossum wrote: > ... > > It is sort of against the rules of the language -- the whole point of > > scoping is that you should be able to define variables even if they > > block a builtin (that you may never have heard of and don't need) from > > view. > > > > But it would be a great feature of PyChecker (for all I know, it > > already does this). > > At least in 0.8.12, which I think is the current release, PyChecker > doesn't diagnose the binding (in global or local scope) of built-in > names with a warning, no. But I think you're right that such a > functionality would belong there. Alex is correct on all counts. It is easy enough to add, so I'll implement it. Neal
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