Message76625
| Author |
gregory.p.smith |
| Recipients |
amaury.forgeotdarc, ggenellina, gregory.p.smith, gvanrossum, jhylton, loewis, romkyns, zanella |
| Date |
2008年11月29日.21:52:14 |
| SpamBayes Score |
0.00033153594 |
| Marked as misclassified |
No |
| Message-id |
<1227995537.0.0.561361490214.issue3826@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Martin: socket.socket has no destructor so a call to
socket.socket._real_close() is not guaranteed. Thats fine as its parent
class from socketmodule.c _socket.socket does the right thing in its
destructor.
Amaury: The case you show doesn't call SOCKETCLOSE() because x still
exists and holds a reference to the socket object.
In order to fix that, SocketIO needs to drop its reference on close.
Take a look at the attached -gps04 patch. It fixes that. |
|