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
Date 2009-04-25.07:44:44
SpamBayes Score 1.0964347e-05
Marked as misclassified No
Message-id <1240645495.72.0.214739361632.issue5835@psf.upfronthosting.co.za>
In-reply-to
Content
PyOS_ascii_formatd is no longer needed, now that we have
PyOS_double_to_string. PyOS_ascii_formatd has a horrible interface,
requiring a format string to be composed and then parsed. The format
string is a very limited printf-like format string.

In 2.7 and 3.1 I'm going to deprecate this function. As a temporary
measure I'm going to create a similar function _PyOS_ascii_formatd (with
a leading underscore) that does not raise a DeprecationWarning and that
takes discrete parameters.

In 2.8 (if it exists) and 3.2 I'll remove PyOS_ascii_formatd.
History
Date User Action Args
2009-04-25 07:44:56eric.smithsetrecipients: + eric.smith, mark.dickinson
2009-04-25 07:44:55eric.smithsetmessageid: <1240645495.72.0.214739361632.issue5835@psf.upfronthosting.co.za>
2009-04-25 07:44:54eric.smithlinkissue5835 messages
2009-04-25 07:44:51eric.smithcreate