diff options
| author | Neil Schemenauer <nascheme@enme.ucalgary.ca> | 2003-07-16 22:19:24 (GMT) |
|---|---|---|
| committer | Neil Schemenauer <nascheme@enme.ucalgary.ca> | 2003-07-16 22:19:24 (GMT) |
| commit | af4c5059d515902c7d2317875f52440b2e7ef253 (patch) | |
| tree | 3a3d0d482cca476172389ce1274effe56cd906fb | |
| parent | 7555294576a642aac7359c51d9b806d17d17a678 (diff) | |
| download | cpython-af4c5059d515902c7d2317875f52440b2e7ef253.zip cpython-af4c5059d515902c7d2317875f52440b2e7ef253.tar.gz cpython-af4c5059d515902c7d2317875f52440b2e7ef253.tar.bz2 | |
Remove code that tried to warn about shadowing builtin names after a
module had been compiled. It gives too many spurious warnings.
| -rw-r--r-- | Misc/NEWS | 6 |
1 files changed, 0 insertions, 6 deletions
@@ -145,12 +145,6 @@ Core and builtins instead of going through __getitem__. If __getitem__ access is preferred, then __iter__ can be overridden. -- Creating an attribute on a module (i.e. a global variable created by - __setattr__) that causes a builtin name to be shadowed now raises a - DeprecationWarning. In future versions of Python the effect may be - undefined (in order to allow for optimization of global and builtin - name lookups). - - SF bug 735247: The staticmethod and super types participate in garbage collection. Before this change, it was possible for leaks to occur in functions with non-global free variables that used these types. |