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 eric.smith
Recipients eric.smith, mark.dickinson, mrabarnett, r.david.murray, skrah
Date 2009-12-02.13:15:10
SpamBayes Score 1.4515997e-05
Marked as misclassified No
Message-id <1259759712.36.0.151983769546.issue7327@psf.upfronthosting.co.za>
In-reply-to
Content
I don't see any documentation that a struct lconv should be interpreted
as UTF-8. In fact Googling "struct lconv utf-8" gives this bug report as
the first hit.

lconv.thousands_sep is char*. It's never been clear to me if this means
"pointer to a single char", or "pointer to a null terminated string of
char". In Objects/stringlib/localeutil.h I treat it as a string of char.
History
Date User Action Args
2009-12-02 13:15:12eric.smithsetrecipients: + eric.smith, mark.dickinson, mrabarnett, r.david.murray, skrah
2009-12-02 13:15:12eric.smithsetmessageid: <1259759712.36.0.151983769546.issue7327@psf.upfronthosting.co.za>
2009-12-02 13:15:11eric.smithlinkissue7327 messages
2009-12-02 13:15:10eric.smithcreate