Micha Reiser e2f7862404 Preserve dangling f-string comments ... <!-- Thank you for contributing to Ruff! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary This PR fixes the issue where the FString formatting dropped dangling comments between the string parts. ```python result_f = ( f' File "{__file__}", line {lineno_f+1}, in f\n' ' f()\n' # XXX: The following line changes depending on whether the tests # are run through the interactive interpreter or with -m # It also varies depending on the platform (stack size) # Fortunately, we don't care about exactness here, so we use regex r' \[Previous line repeated (\d+) more times\]' '\n' 'RecursionError: maximum recursion depth exceeded\n' ) ``` The solution here isn't ideal because it re-introduces the `enclosing_parent` on `DecoratedComment` but it is the easiest fix that I could come up. I didn't spend more time finding another solution becaues I think we have to re-write most of the fstring formatting with the upcoming Python 3.12 support (because lexing the individual parts as we do now will no longer work). closes #6440 <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan `cargo test` The child PR testing that all comments are formatted should now pass		2023-08-10 09:11:25 +02:00
..
snapshots	Preserve dangling f-string comments	2023-08-10 09:11:25 +02:00
fixtures.rs	Formatter: Add SourceType to context to enable special formatting for stub files (#6331)	2023-08-04 11:52:26 +00:00