homepage

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 lemburg
Recipients doerwalter, ezio.melotti, lemburg, ncoghlan, serhiy.storchaka, vstinner
Date 2013年11月22日.11:24:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <528F3ED7.1010008@egenix.com>
In-reply-to <CADiSq7fNnQqQoSFp5cKgUTeFE6Y+aRwSWVw_g_JGU14x6mE3YQ@mail.gmail.com>
Content
Nick: I've had a look at your second patch. A couple of notes:
 * 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.
 * The comment in codecs.h should read:
 """
 Checks the encoding against a list of codecs which do not
 implement a str<->bytes encoding before attempting the
 operation.
 Please note that these APIs are internal and should not
 be used in Python C extensions.
 """
Regarding Victor's suggestion to use a separate registry dict
for this: I'm definitely -1 on this.
The black listing is a very special case only used for the
.encode()/.decode() methods and otherwise doesn't have anything to do
with the codecs sub-system. It doesn't make sense to change the design
of the registry just to implement this one special case.
History
Date User Action Args
2013年11月22日 11:24:16lemburgsetrecipients: + lemburg, doerwalter, ncoghlan, vstinner, ezio.melotti, serhiy.storchaka
2013年11月22日 11:24:16lemburglinkissue19619 messages
2013年11月22日 11:24:15lemburgcreate

AltStyle によって変換されたページ (->オリジナル) /