[issue7168] Document PyFloat_AsString and PyFloat_AsReprString as deprecated and unsafe

Eric Smith added the comment: A slightly improved version checked in as r75510. -- resolution: -> accepted stage: patch review -> committed/rejected status: open -> closed ___ Python tracker __

[issue7168] Document PyFloat_AsString and PyFloat_AsReprString as deprecated and unsafe

Changes by Eric Smith : Removed file: http://bugs.python.org/file15164/issue7168.patch ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7168] Document PyFloat_AsString and PyFloat_AsReprString as deprecated and unsafe

Eric Smith added the comment: Updated patch based on Georg's input. -- Added file: http://bugs.python.org/file15166/issue7168.patch ___ Python tracker ___ ___

[issue7168] Document PyFloat_AsString and PyFloat_AsReprString as deprecated and unsafe

Eric Smith added the comment: Proposed patch attached. -- keywords: +patch stage: -> patch review Added file: http://bugs.python.org/file15164/issue7168.patch ___ Python tracker ___

[issue7168] Document PyFloat_AsString and PyFloat_AsReprString as deprecated and unsafe

Changes by Eric Smith : -- assignee: georg.brandl -> eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7168] Document PyFloat_AsString and PyFloat_AsReprString as deprecated and unsafe

New submission from Eric Smith : These functions are unsafe and I'd like to delete them. They've already been deleted in py3k, per PEP 3100. They are no longer used internally to the interpreter. They should be documented as deprecated and as unsafe. They write to a char* parameter, but don't ta