| commit | 19f44560f2387fd0f7e7f6b459510428216b6f79 | [log] [tgz] |
|---|---|---|
| author | Guido van Rossum <guido@python.org> | Tue Nov 04 17:32:59 1997 +0000 |
| committer | Guido van Rossum <guido@python.org> | Tue Nov 04 17:32:59 1997 +0000 |
| tree | 9e8499101ed8e6818c703429952a6fcaa9006753 | |
| parent | 8f3c812e22d1fc2a70c1f1c2b56262553e8d9c34 [diff] |
Use ``0'' instead of ``None'' to reset the underlying object in close methods. Using None causes problems if the destructor is called after the __builtin__ module has already been destroyed (unfortunately, this can happen!). I can't just delete the object because it is actually tested for (if self._sock: ...). Setting it to 0 is a bit weird but works.