summaryrefslogtreecommitdiffstats
path: root/Doc/library/string.rst
Commit message (Collapse)AuthorAgeFilesLines
* [3.11] gh-110631: Fix reST indentation in `Doc/library` (GH-110685) (#110737)Ezio Melotti2023-10-111-50/+50
| | | | | | | | | | * [3.11] gh-110631: Fix reST indentation in `Doc/library` (GH-110685) Fix wrong indentation in the Doc/library dir.. (cherry picked from commit bb7923f556537a463c403dc1097726d8a8e1a6f2) Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com> * Fix merge glitch.
* [3.11] GH-95088: Clarify rules for parsing an item key for format strings ↵Miss Islington (bot)2023-06-071-1/+3
| | | | | | | | | | (GH-103779) (#105418) GH-95088: Clarify rules for parsing an item key for format strings (GH-103779) (cherry picked from commit 3e7316d7e8969febb56fbc7416d483b073bd1702) Co-authored-by: achhina <amanschhina@gmail.com> Co-authored-by: Łukasz Langa <lukasz@langa.pl> Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
* Quote literal tokens in standard format specifier grammar (GH-102902)Miss Islington (bot)2023-03-311-1/+1
| | | | | | Reported by Damian Dureck: https://mail.python.org/archives/list/docs@python.org/thread/UZTWBJIXC3MBKTHXVTIBPGDPKBNWZ5LN/ (cherry picked from commit f6405a46627e1f74c279f712c8776a165b0ba9fd) Co-authored-by: Petr Viktorin <encukou@gmail.com>
* GH-95685: Fix rendering of the string documentation (GH-95686) (GH-95700)Miss Islington (bot)2022-08-051-0/+1
| | | | | | | | There's an extra underlines that messed the rest of the documentation rendering. Closes #95685 (cherry picked from commit a525f2ada407d6677bf8ca708f104694de0525e4) Co-authored-by: Mariatta Wijaya <Mariatta@users.noreply.github.com>
* [3.11] gh-91838: Use HTTPS links in docs for resources which redirect to ↵Serhiy Storchaka2022-08-041-1/+1
| | | | | | | | | | | | HTTPS (GH-95527) (GH-95643) If an HTTP link is redirected to a same looking HTTPS link, the latter can be used directly without changes in readability and behavior. It protects from a men-in-the-middle attack. This change does not affect Python examples.. (cherry picked from commit f79547a429d5c90af83a0da821e082cba20d4712) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
* bpo-45995: add "z" format specifer to coerce negative 0 to zero (GH-30049)John Belmonte2022-04-111-1/+10
| | | | | | | | Add "z" format specifier to coerce negative 0 to zero. See https://github.com/python/cpython/issues/90153 (originally https://bugs.python.org/issue45995) for discussion. This covers `str.format()` and f-strings. Old-style string interpolation is not supported. Co-authored-by: Mark Dickinson <dickinsm@gmail.com>
* Corrections to format precision description. (GH-31291)John Belmonte2022-02-141-5/+6
| | | | | | | | | | | * `precision` field is a decimal integer * clarify that stated limitations are on presentation type rather than input value type. Especially misleading is "precision is not allowed for integer values", since integer value input to a format like `.1f` is fine. * regarding max field size, replace "non-number" with "string", which is the only non-numeric presentation type Automerge-Triggered-By: GH:ericvsmith
* bpo-46307: Add string.Template.get_identifiers() method (GH-30493)Ben Kehoe2022-01-111-0/+19
| | | | | Add `string.Template.get_identifiers()` method that returns the identifiers within the template. By default, raises an error if it encounters an invalid identifier (like `substitute()`). The keyword-only argument `raise_on_invalid` can be set to `False` to ignore invalid identifiers (like `safe_substitute()`). Automerge-Triggered-By: GH:warsaw
* docs: clearly document that ":#X" string formatting results in "0X..." ↵Tal Einat2021-05-061-2/+4
| | | | | | | (GH-25941) * clearly document that ":#X" string formatting results in "0X..." * put back the "serial comma"
* bpo-31907: [doc] clarify that str.format() does not support arbitrary ↵Irit Katriel2021-03-281-2/+2
| | | | expressions (#25053)
* bpo-27772: Make preceding width with 0 valid in string format. (GH-11270)Serhiy Storchaka2021-01-251-2/+6
| | | | Previously it was an error with confusing error message.
* bpo-39096: Format specification documentation fixes for numeric types (GH-23575)Mark Dickinson2020-12-181-12/+23
|
* bpo-39096: Improve description of 'e', 'f' and 'g' presentation types (#23537)Mark Dickinson2020-11-291-12/+31
| | | | | | | | | | | * Improve description of 'e', 'f' and 'g' presentation types * Drop the 'E' from Scientific 'E' notation; remove >= 0 qualifications * Fix false statement that the alternate form is valid for Decimal * Nitpick: remove the Harvard/Oxford comma * Add note that the decimal point is also removed if no digits follow it, except in alternate form
* bpo-41762: Fix usage of productionlist markup in the doc (GH-22281)Victor Stinner2020-09-181-2/+2
| | | | | | | Use an unique identifier for the different grammars documented using the Sphinx productionlist markup. productionlist markups of the same grammar, like "expressions" or "compound statements", use the same identifier "python-grammar".
* bpo-40204: Fix duplicated productionlist names in the doc (GH-21900)Victor Stinner2020-08-171-1/+1
| | | | | | | | Sphinx 3 disallows having more than one productionlist markup with the same name. Simply remove names in this case, since names are not shown anyway. For example, fix the Sphinx 3 warning: Doc/reference/introduction.rst:96: duplicate token description of *:name, other instance in reference/expressions
* bpo-13790: Change 'string' to 'specification' in format doc (GH-18690)Terry Jan Reedy2020-02-281-2/+2
|
* bpo-38657: Clarify numeric padding behaviour in string formatting (GH-17036)Pete Wicken2020-02-211-2/+3
| | | | | | | | | | | Make the definition of the width more explicit that it includes any extra signs added by other options. https://bugs.python.org/issue38657 Automerge-Triggered-By: @Mariatta
* bpo-32790: Add info about alt format using # for 'g' in chart (GH-6624)bchhabra24902019-09-131-1/+2
|
* bpo-23460: Fix documentation for decimal string :g formatting (GH-11850)Brennan D Baraban2019-09-111-3/+4
|
* bpo-36168: Lowercase the word "subsequent" in get_value doc (GH-14485)Krishna Oza2019-07-011-1/+1
| | | | | Subsequent -> subsequent https://bugs.python.org/issue36168
* bpo-37116: Use PEP 570 syntax for positional-only parameters. (GH-13700)Serhiy Storchaka2019-06-011-3/+3
|
* Document actual string.punctuation value. (GH-12270)Andre Delfino2019-03-141-2/+1
|
* Correct grammar mistakes in string.rst. (GH-9752)Andrés Delfino2018-11-071-2/+2
|
* bpo-35110: Fix unintentional spaces around hyphens and dashes. (GH-10231)Serhiy Storchaka2018-10-311-4/+4
|
* bpo-35054: Add yet more index entries for symbols. (GH-10121)Serhiy Storchaka2018-10-281-17/+15
|
* bpo-35054: Add more index entries for symbols. (GH-10064)Serhiy Storchaka2018-10-261-0/+28
|
* bpo-34273: Change 'Fixed point' to 'Fixed-point notation'. (#8673)Terry Jan Reedy2018-08-061-4/+4
| | | | | | | | | | | | | | | * bpo-34273: Change 'Fixed point' to 'Fixed-point notation'. The change in the mini language floating point and decimal table is consistent with 'Exponential notation' and clarifies that we are referring to the output notation, not an object type. * Update string.rst * Update string.rst * Update string.rst * Update string.rst
* bpo-33828: Add missing versionchanged note for string.Formatter. (GH-7668)Xiang Zhang2018-06-131-2/+5
| | | | | string.Formatter auto-numbering feature was added in 3.4 and there is no versionchanged note in its documentation, making the documentation ambiguous about which version the feature is available.
* bpo-32720: Fixed the replacement field grammar documentation. (GH-5544)Mariatta2018-02-051-2/+2
| | | | `arg_name` and `element_index` are defined as `digit`+ instead of `integer`.
* bpo-32720: Fixed the definition for width and precision in format ↵nathankerr962018-02-041-2/+2
| | | | | mini-language doc (GH-5482) Changed the definition of width and precision from "integer" to "digit+" in format mini-language doc.
* bpo-31672: Restore the former behavior when override flags in Template. (#5099)Serhiy Storchaka2018-01-041-7/+2
| | | | Overriding flags to 0 will make the default pattern matching only lower case letters.
* bpo-31672 - Add one last minor clarification for idpattern (#4483)Barry Warsaw2017-11-211-2/+4
| | | Add one last minor clarification for idpattern
* bpo-31672: doc: Remove one sentence from library/string.rst (GH-3990)INADA Naoki2017-10-141-1/+1
| | | | This sentence is removed while backporting to 3.6 branch. See https://github.com/python/cpython/pull/3982#discussion_r144555768
* bpo-31672: Fix string.Template accidentally matched non-ASCII identifiers ↵INADA Naoki2017-10-131-2/+11
| | | | | | | | | | | (GH-3872) Pattern `[a-z]` with `IGNORECASE` flag can match to some non-ASCII characters. Straightforward solution for this is using `IGNORECASE | ASCII` flag. But users may subclass `Template` and override only `idpattern`. So we want to avoid changing `Template.flags`. So this commit uses local flag `-i` for `idpattern` and change `[a-z]` to `[a-zA-Z]`.
* bpo-1198569: Allow string.Template braced pattern to be different (#3288)Barry Warsaw2017-09-041-3/+15
| | | | | | | | * bpo-1198569: Allow the braced pattern to be different ``string.Template`` subclasses can optionally define ``braceidpattern`` if they want to specify different placeholder patterns inside and outside the braces. If None (the default) it falls back to ``idpattern``.
* Improve the documentation for template strings (#856)Barry Warsaw2017-03-281-11/+19
| | | | | bpo-19824 bpo-20314 bpo-12518
* Issue #29193: A format string argument for string.Formatter.format()Serhiy Storchaka2017-01-131-3/+3
| | | | is now positional-only.
* Issue #19795: Mark up None as literal text.Serhiy Storchaka2016-10-191-1/+1
|\
| * Issue #19795: Mark up None as literal text.Serhiy Storchaka2016-10-191-1/+1
| |
* | Further improved ',' and '_' specification in format mini-language.Eric V. Smith2016-09-101-2/+2
| |
* | Improved ',' and '_' specification in format mini-language.Eric V. Smith2016-09-101-1/+2
| |
* | Issue 27080: PEP 515: add '_' formatting option.Eric V. Smith2016-09-101-1/+11
| |
* | Issue #23921: Standardized documentation whitespace formatting.Serhiy Storchaka2016-05-101-6/+6
|\ \ | |/ | | | | Original patch by James Edwards.
| * Issue #23921: Standardized documentation whitespace formatting.Serhiy Storchaka2016-05-101-6/+6
| | | | | | | | Original patch by James Edwards.
* | Merge with 3.5Terry Jan Reedy2016-03-211-2/+4
|\ \ | |/
| * Issue #15660: Further clarify 0 prefix for width specifier in formats.Terry Jan Reedy2016-03-211-2/+4
| |
* | Issue #25179: Documentation for formatted string literals aka f-stringsMartin Panter2016-02-131-3/+7
|/ | | | | Some of the inspiration and wording is taken from the text of PEP 498 by Eric V. Smith, and the existing str.format() documentation.
* Issue #25179: Preparatory cleanup of existing docs on string formattingMartin Panter2016-02-081-12/+15
| | | | | | | | | * Various sections were pointing to the section on the string.Formatter class, when the section on the common format string syntax is probably more appropriate * Fix references to various format() functions and methods * Nested replacement fields may contain conversions and format specifiers, and this is tested; see Issue #19729 for instance
* - Issue #24351: Clarify what is meant by "identifier" in the context ofBarry Warsaw2015-06-091-6/+8
|\ | | | | | | string.Template instances.
| * - Issue #24351: Clarify what is meant by "identifier" in the context ofBarry Warsaw2015-06-091-6/+8
| | | | | | | | string.Template instances.