Skip to content

Rename symbol misses symbols in formatted strings f"{foo}" #187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DonJayamanne opened this issue Nov 14, 2017 · 11 comments
Closed

Rename symbol misses symbols in formatted strings f"{foo}" #187

DonJayamanne opened this issue Nov 14, 2017 · 11 comments
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@DonJayamanne
Copy link

From @sdwarwick on September 25, 2017 13:25

Environment data

VS Code version: 1.16.1
Python Extension version: 0.7.0
Python Version: 3.6
OS and version: windows 10

Actual behavior

rename/refactor symbols completely misses symbols inside formatted text strings
f"{name}"

name is not found or changed

Expected behavior

clear from above

Steps to reproduce:

Logs

Output from Python output panel

no output

Output from Console window (Help->Developer Tools menu)

no output

Copied from original issue: DonJayamanne/pythonVSCode#1237

@DonJayamanne
Copy link
Author

From @kodalipraveen on October 13, 2017 19:16

This issue is also seen in Mac OS
VSCode - 1.17.1
Python Extension - 0.7.0

@brettcannon brettcannon added awaiting 1-verification bug Issue identified by VS Code Team member as probable bug labels Nov 14, 2017
@ericsnowcurrently ericsnowcurrently self-assigned this Jan 11, 2018
@MikhailArkhipov
Copy link

Same as #344, specifically davidhalter/jedi#930

@MikhailArkhipov
Copy link

#1418, Jedi 0.12

@brettcannon
Copy link
Member

This is actually still failing for me. If I have:

thing = 42
print(f'hello, {thing}')

and I attempt a Rename Symbol on thing, it misses the f-string.

@FlavioCestari
Copy link

Waiting for this fix too. :)

@brettcannon
Copy link
Member

@FlavioCestari this is going to require an upstream fix from rope.

@FlavioCestari
Copy link

It looks like the project is kind of stopped. The last release was in August, 2017.
https://github.com/python-rope/rope/releases

Is there any alternative?

@brettcannon
Copy link
Member

Not at the moment. We are hoping to get our new analysis engine to handle refactorings/renamings.

@kleinicke

This comment has been minimized.

@ikariwing
Copy link

FYI (Info from @legnaleurc): @orn688 already wrote a PR for rope to improve the symbol replacement in f-string , that PR is still not merged though. Thanks @orn688 :)

@DonJayamanne
Copy link
Author

Closing, as this has been resolved upstream in rope.

@ghost ghost removed the needs upstream fix label Apr 18, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

7 participants