[issue1519] async_chat.__init__() parameters

Josiah Carlson <[EMAIL PROTECTED]> added the comment: Fixed for 2.6 in changelist 64768. Fixed for 3.0 in changelist 64770. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> _

[issue1519] async_chat.__init__() parameters

Changes by A.M. Kuchling: -- assignee: -> josiahcarlson nosy: +josiahcarlson __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing lis

[issue1519] async_chat.__init__() parameters

Nadeem Vawda added the comment: Thanks for pointing that out; I've uploaded a second patch that changes async_chat.__init__() to use 'sock' instead of 'conn'. This change shouldn't affect anything either, since the argument is simply passed to asyncore.dispatcher.__init__(). Added file: http:/

[issue1519] async_chat.__init__() parameters

billiejoex added the comment: +1. Another inconsistency are the argument names used in __init__ methods, one called "sock" and the other called "conn": asyncore: def __init__(self, sock=None, map=None): asynchat: def __init__ (self, conn=None): -- nosy: +billiejoex ___

[issue1519] async_chat.__init__() parameters

New submission from Nadeem Vawda: The __init__() function for asynchat.async_chat doesn't allow the caller to specify a channel map. I thought it would make sense to add an optional 'map' parameter, for consistency with asyncore.dispatcher. If the parameter is not specified, asyncore.dispatcher