Message 146642 - Python tracker

➜

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.

In-reply-to
Author	xdegaye
Recipients	François-Xavier.Bourlet, neologix, xdegaye
Date	2011年10月30日.15:59:53
SpamBayes Score	3.6835755e-07
Marked as misclassified	No
Message-id	<1319990394.56.0.309115728448.issue12498@psf.upfronthosting.co.za>

Content
> Note that the patch may break applications that have given different > semantics to 'closing' ('closing' being such a common name for a > network application) after they noticed that this attribute is never > used by asyncore nor by asynchat. I was thinking about the discussion in issue 1641, the second part of the discussion starting with msg 84972. The attached patch uses another name and drains the output buffer only on a close event, not on error conditions. I will do the patch for asynchat and do both test cases, unless you beat me to it.

Content

> Note that the patch may break applications that have given different
> semantics to 'closing' ('closing' being such a common name for a
> network application) after they noticed that this attribute is never
> used by asyncore nor by asynchat.
I was thinking about the discussion in issue 1641, the second part of
the discussion starting with msg 84972.
The attached patch uses another name and drains the output buffer only
on a close event, not on error conditions.
I will do the patch for asynchat and do both test cases, unless you
beat me to it.

History
Date	User	Action	Args
2011年10月30日 15:59:54	xdegaye	set	recipients: + xdegaye, neologix, François-Xavier.Bourlet
2011年10月30日 15:59:54	xdegaye	set	messageid: <1319990394.56.0.309115728448.issue12498@psf.upfronthosting.co.za>
2011年10月30日 15:59:53	xdegaye	link	issue12498 messages
2011年10月30日 15:59:53	xdegaye	create

homepage