[issue29526] Documenting format() function

Change by Eric V. Smith : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue29526] Documenting format() function

Irit Katriel added the comment: It looks like this is complete and can be closed. -- nosy: +iritkatriel ___ Python tracker ___ ___

[issue29526] Documenting format() function

Serhiy Storchaka added the comment: New changeset 6ed7aff8948e50708f048f3f7fd41809259d1777 by Serhiy Storchaka in branch '2.7': [2.7] bpo-29526: Add reference to help('FORMATTING') in format() builtin (GH-166). (#3492)

[issue29526] Documenting format() function

Serhiy Storchaka added the comment: New changeset c67838da2cde6fa3f1bef11f08719237983e6990 by Serhiy Storchaka in branch '3.6': [3.6] bpo-29526: Add reference to help('FORMATTING') in format() builtin (GH-166). (#3491)

[issue29526] Documenting format() function

Changes by Serhiy Storchaka : -- versions: +Python 2.7 -Python 3.5 ___ Python tracker ___

[issue29526] Documenting format() function

Changes by Serhiy Storchaka : -- pull_requests: +3485 ___ Python tracker ___

[issue29526] Documenting format() function

Changes by Serhiy Storchaka : -- keywords: +patch pull_requests: +3484 stage: -> patch review ___ Python tracker ___

[issue29526] Documenting format() function

Changes by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list

[issue29526] Documenting format() function

Changes by Amit Kumar : -- pull_requests: +130 ___ Python tracker ___ ___

[issue29526] Documenting format() function

Terry J. Reedy added the comment: +1 of Serhiy's ideas. I was not aware that FORMATTING had been added. And this could be specifically helpful. >>> help(int.__format__) Help on method_descriptor: __format__(...) default object formatter -- nosy: +terry.reedy

[issue29526] Documenting format() function

Hugo Prod'homme added the comment: +1 : Adding the reference to help('FORMATTING') will indeed solve all the problems I was thinking about at first. -- I realized I was thinking only about a small part of the problem thanks to your answers. I wasn't even thinking about the dates and other

[issue29526] Documenting format() function

R. David Murray added the comment: Serhiy: those are both great ideas. +1 from me too. Then we can even have the date formatting documented without cluttering up the main docstring, if we wish :) The format docstring should then also mention doing help on the __format__ method of concrete

[issue29526] Documenting format() function

Marco Buttu added the comment: > It may be worth to add a reference to FORMATTING from the > format() docstring. +1 :-) -- nosy: +marco.buttu ___ Python tracker

[issue29526] Documenting format() function

Serhiy Storchaka added the comment: I think it would be worth to extend docstrings of __format__ methods of concrete types for including the description of type-specific format specifiers. But the docstring of format() shouldn't contain the description of format specifiers of all builtin

[issue29526] Documenting format() function

R. David Murray added the comment: Thanks for wanting to help improve python. I'm not entirely clear on what you are proposing. I *think* you want to add something to the 'format' docstring? As Eric mentioned the 'mini language' depends on the datatype, so it is going to be hard to cram

[issue29526] Documenting format() function

Eric V. Smith added the comment: Since these codes don't apply to all types, you'll need some words saying what they do apply to. For example, None being the same as "g" is true for int, float, and Decimal; but None is "s" for strings. And, for example, none of the listed codes apply to

[issue29526] Documenting format() function

New submission from Hugo Prod'homme: Hello python contributors, this is my first time on python.org and I am coming with a suggestion. The idea is to help people that have to format strings containing numbers of various kinds, I am from the scientific domain but this should help everybody