[issue3764] asyncore differences between 2.x and 3.x

Giampaolo Rodola' <[EMAIL PROTECTED]> added the comment: Sorry, my fault. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue3764] asyncore differences between 2.x and 3.x

Josiah Carlson <[EMAIL PROTECTED]> added the comment: I reverted the change I made to 2.6, see 66282. The handle_close_event() method also doesn't exist in 3.0, which is why it (and the reference) were removed in revision 64883. Giampaolo needs to update his Python 3.0 checkout. Closing as i

[issue3764] asyncore differences between 2.x and 3.x

Changes by Gregory P. Smith <[EMAIL PROTECTED]>: -- keywords: +easy type: -> behavior versions: +Python 2.6 -Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3764] asyncore differences between 2.x and 3.x

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: please undo this, this broke asyncore in trunk. handle_close_event doesn't exist in 2.6. -- nosy: +gregory.p.smith priority: -> release blocker resolution: fixed -> status: closed -> open ___

[issue3764] asyncore differences between 2.x and 3.x

Josiah Carlson <[EMAIL PROTECTED]> added the comment: Fixed in 66281. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3764] asyncore differences between 2.x and 3.x

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: -> josiahcarlson ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-b

[issue3764] asyncore differences between 2.x and 3.x

New submission from Giampaolo Rodola' <[EMAIL PROTECTED]>: I don't know if this is intentional but I point it out anyway in case this is wrong (as I think): asyncore.py of Python 2.6 trunk on line 104 contains: if flags & select.POLLHUP: obj.handle_close() ...while the pyth