[issue41045] f-string's "debug" feature is undocumented

Guido van Rossum added the comment: Thanks Ama Aje My Fren! You can transfer your other PR to a different bpo issue by editing the subject on GitHub. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python

[issue41045] f-string's "debug" feature is undocumented

Guido van Rossum added the comment: New changeset 3baff21f5bb8db7fa1c15788a8f82fa040a90d5d by Guido van Rossum in branch '3.8': [3.8] bpo-41045: Document debug feature of f-strings ('=') (GH-21509) (#21647) https://github.com/python/cpython/commit/3baff21f5bb8db7fa1c15788a8f82fa040a90d5d

[issue41045] f-string's "debug" feature is undocumented

Change by Guido van Rossum : -- pull_requests: +20786 pull_request: https://github.com/python/cpython/pull/21647 ___ Python tracker ___

[issue41045] f-string's "debug" feature is undocumented

Guido van Rossum added the comment: New changeset e962e3f65a086d9d3b848483fd01215d96ecc5f9 by Guido van Rossum in branch '3.9': [3.9] bpo-41045: Document debug feature of f-strings ('=') (GH-21509) (GH-21645) https://github.com/python/cpython/commit/e962e3f65a086d9d3b848483fd01215d96ecc5f9

[issue41045] f-string's "debug" feature is undocumented

Change by Guido van Rossum : -- pull_requests: +20785 pull_request: https://github.com/python/cpython/pull/21645 ___ Python tracker ___

[issue41045] f-string's "debug" feature is undocumented

Change by miss-islington : -- pull_requests: +20784 pull_request: https://github.com/python/cpython/pull/21644 ___ Python tracker ___

[issue41045] f-string's "debug" feature is undocumented

miss-islington added the comment: New changeset 13efaec2e03288d7ff0ee643589c32bde6c6973c by amaajemyfren in branch 'master': bpo-41045: Document debug feature of f-strings ('=') (GH-21509) https://github.com/python/cpython/commit/13efaec2e03288d7ff0ee643589c32bde6c6973c -- nosy:

[issue41045] f-string's "debug" feature is undocumented

Guido van Rossum added the comment: I think your PR 21552 and any work you're doing on pydoc could go under the new issue 41411 that Ezio just opened. -- ___ Python tracker

[issue41045] f-string's "debug" feature is undocumented

Ama Aje My Fren added the comment: > then we can merge that one and close *this* issue. I am looking at the pydoc issue now. It will take me more than an hour but I will figure it. Can that be under this issue also or (since you raised it as an OT) make that another issue? --

[issue41045] f-string's "debug" feature is undocumented

Ezio Melotti added the comment: > I agree that it might be better to separate them into a new issue. I created #41411. -- ___ Python tracker ___

[issue41045] f-string's "debug" feature is undocumented

Guido van Rossum added the comment: Those are really good observations and proposals, Ezio! I agree that it might be better to separate them into a new issue. Can you also review https://github.com/python/cpython/pull/21552 (the second PR here by amaajemyfren)? Maybe it would actually make

[issue41045] f-string's "debug" feature is undocumented

Ezio Melotti added the comment: I was just just trying to link to someone the documentation for f-strings, but: 1) Searching "fstring" only returns two results about xdrlib[0]; 2) Searching "f-string" returns many unrelated results[1]; 3) The first (and closer) result (string -- Common string

[issue41045] f-string's "debug" feature is undocumented

Guido van Rossum added the comment: I've reviewed your first PR (#21509). Regarding your second one, I think there's a misunderstanding. With "pydoc" I didn't mean "the Python docs". IMO the documentation of f-strings in the language reference is sufficient, there's no need for another

[issue41045] f-string's "debug" feature is undocumented

Ama Aje My Fren added the comment: Hello all, I have attempted to resolve this issue by adding some comments to PR21464 and later provided a reworded PR21509 that attempts to resolve this using ideas from @rishi93. Finally I have tried to document f-string within pydoc itself with PR21552.

[issue41045] f-string's "debug" feature is undocumented

Change by Ama Aje My Fren : -- pull_requests: +20698 pull_request: https://github.com/python/cpython/pull/21552 ___ Python tracker ___

[issue41045] f-string's "debug" feature is undocumented

Change by Ama Aje My Fren : -- nosy: +amaajemyfren nosy_count: 5.0 -> 6.0 pull_requests: +20645 pull_request: https://github.com/python/cpython/pull/21509 ___ Python tracker

[issue41045] f-string's "debug" feature is undocumented

Change by Emmanuel Arias : -- nosy: +eamanu ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41045] f-string's "debug" feature is undocumented

Rajarishi Devarajan added the comment: Thank you very much. I have made a pull request. Looking forward to your review on my first open-source contribution :) -- ___ Python tracker

[issue41045] f-string's "debug" feature is undocumented

Change by Rajarishi Devarajan : -- keywords: +patch pull_requests: +20612 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/21464 ___ Python tracker

[issue41045] f-string's "debug" feature is undocumented

Eric V. Smith added the comment: @rishi93: yes, please do! -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue41045] f-string's "debug" feature is undocumented

Rishi added the comment: Hello all, Could I help by adding this to the documentation ? -- nosy: +rishi93 ___ Python tracker ___

[issue41045] f-string's "debug" feature is undocumented

Guido van Rossum added the comment: Every other detail about f-strings is spelled out meticulously in the reference manual: https://docs.python.org/3/reference/lexical_analysis.html#formatted-string-literals I think it needs to be added here. PS OT: I can't find anything about f-strings in

[issue41045] f-string's "debug" feature is undocumented

New submission from Eric V. Smith : The feature of f-strings using '=' for "debugging" formatting is not documented. >>> foo = 'bar' >>> f'{foo=}' "foo='bar'" I'm not sure where this should fit in to the documentation, but it needs to be in there somewhere. Basically the documentation