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.

Author serhiy.storchaka
Recipients doerwalter, ezio.melotti, lemburg, ncoghlan, python-dev, serhiy.storchaka, vstinner
Date 2013-11-22.19:24:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1976788.6iTZbMbQgu@raxxla>
In-reply-to <>
>  * I think you should add the flag to the constructor of the CodecInfo
>    tuple subclass and then set this in the resp. codecs. The extra
>    constructor class method looks too much like a hack and is
>    not needed.

I think that adding new keyword argument to public function is much worse than 
adding new private class method or private module level function. Arguments 
are always visible, while private methods and functions are usually hidden. 
New argument will confuse users.
Date User Action Args
2013-11-22 19:24:39serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, doerwalter, ncoghlan, vstinner, ezio.melotti, python-dev
2013-11-22 19:24:39serhiy.storchakalinkissue19619 messages
2013-11-22 19:24:39serhiy.storchakacreate