This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author perrygreenfield
Recipients
Date 2003-09-17.21:16:55
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
It appears that 2.3 changed how socket.close() works. 
We now find errors when terminating Python when we 
reference socket.close() in a __del__ method. We have 
worked around it by removing calls to socket.close() but 
note the following differences between the same section 
of code between 2.2 and 2.3 which suggest that the 2.3 
behavior is not ideal and should be fixed.

In Python 2.3:

    def close(self):
        self._sock = _closedsocket()
        self.send = self.recv = self.sendto = self.recvfrom \
                        = self._sock._dummy

In Python 2.2:

    def close(self):
        # Avoid referencing globals here
        self._sock = self.__class__._closedsocket()

Note the reference to avoiding globals which is 
presumably the source of the problem with 2.3. Perhaps 
I'm naive but I would guess that calling a close method 
should be considered a safe operation for use in a 
__del__ method.
History
Date User Action Args
2008-01-20 09:56:22adminlinkissue808164 messages
2008-01-20 09:56:22admincreate