Skip to content

Handle the edge case where an f-string looks like f"#{some_var}" - #808

Open
rlbr wants to merge 2 commits into
python-rope:masterfrom
rlbr:master
Open

rlbr wants to merge 2 commits into
python-rope:masterfrom
rlbr:master

Conversation

@rlbr

@rlbr rlbr commented Dec 2, 2024 •

Copy link
Copy Markdown

Description

Fixes broken behavior with specific f-strings

Fixes #807

@rlbr rlbr changed the title Added test with fstring Handle the edge case where an f-string looks like f"#{some_var}" Dec 3, 2024
@rlbr

rlbr commented Dec 3, 2024 •

Copy link
Copy Markdown
Author

All tests passed on my machine

marlon-costa-dc pushed a commit to marlon-costa-dc/rope that referenced this pull request Sep 25, 2026
Fork of upstream 1.14.0 with the datacosmos integration: PEP 695 type
parameters, full signature tokens, f-string delimiter fixes and the
adopted upstream PRs python-rope#808, python-rope#837, python-rope#858, python-rope#865, python-rope#867, python-rope#868, python-rope#874, python-rope#880.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rope exception when f-string has a # before a variable when using extract method

1 participant