[IronPython] Socket's life after close()
sanxiyn at gmail.com
Thu Jan 18 22:47:51 PST 2007
Issue #1368 is closed, but its primary use case is still broken. Have
you tested with original poster's test case, urllib.urlopen()?
amecha commented on Jan 10 about this closed issue stating that it is
still broken and I can confirm. (btw, shouldn't the original poster be
able to re-open the bug?)
Here is a simplifed test case since urllib.urlopen() calls hosts of
other functions that simply obscures the root cause. The test assumes
that echo service is enabled on the localhost.
s = socket.socket()
f = s.makefile()
Python can read fine after socket close(), but IronPython complains.
More information about the users