Add refactoring features like change in file, module and variable names

[qb-tarushg]

Environment data

• VS Code version: XXX
• Extension version (available under the Extensions sidebar): XXX
• OS and version: XXX
• Python version (& distribution if applicable, e.g. Anaconda): XXX
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): XXX
• Relevant/affected Python packages and their versions: XXX

Expected behaviour

XXX

Actual behaviour

XXX

Steps to reproduce:

1. XXX

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

XXX

[DonJayamanne]

@qb-tarushg

• Refactor rename file/module (this is new, and not yet supported)
• Refactor rename function (this is currently supported)

[ispmarin]

👍

[awaemmanuel]

👍

[HitLuca]

Having to open PyCharm whenever I need to refactor some files is not the most efficient workflow

[luabud]

This should also captures variable name refactoring

[astier]

Refactoring of a file should include renaming and moving it to another directory.

[ricky-lim]

👍

[mscipio]

This missing feature migth single-handedly send me back to PyCharm ... :\

[lescientifik]

To add to this topic, I have to say I switch from vs code to pycharm recently, despite loving code so far. The refactoring option in pycharm is indeed a killer feature, badly missing in vs code. That's too bad because vs code is way lighter, easier to use and uncluttered...

So +1 for this feature, would love to see this happen!

[akiyamasho]

+1 for this as well. I switched to VSCode since we use the Live Share a lot with my team, so having this would completely replace PyCharm for most devs

[jakebailey]

Just to explicitly list things here:

• We support variable renaming already (F2)
• Renaming modules/files, no, but that may be Automatically update import paths when you move or rename a python file #127.

[jakebailey]

I think I'm going to close this in favor of #127 (as noted above); we're working on it.

[tomc-goodrx]

@jakebailey FWIW I'm pretty sure #127 won't solve the thing I need right now (that PyCharm does). That is breaking the stuff (functions, consts, classes, etc) up in some file into a bunch of smaller files and renaming the references.

It's pretty similar conceptually to rename symbol, but since each other file in the workspace has some reference to the current module it's mostly about easily updating those.

Since #127 operates on a file level I don't think it will help with actual refactoring.