Hi@lieryan sorry for thevery long time to review it.
Can you post here a sample code and instructions for us to test it?

Hi@diraol, thanks for looking into this. The changed behavior here does not actually depend on the text on the Vim buffer, so it shouldn't matter what the code you have on the python file for testing this change. In any case, in the places where I've removed the in-hierarchy option, currently python-mode never passes those options to rope anyway (for example).

If you want a code sample that demonstrates what the in_hierarchy does though, it basically changes how rope finds members of a class that belongs to a class inheritance hierarchy:

classFruit(abc.ABC):defeat(self):passclassApple(Fruit):defeat(self):passclassOrange(Fruit):defeat(self):pass

Whenin_hierarchy=True, when renamingOrange.eat(), bothFruit.eat(),Apple.eat(), are considered the "same" symbol, so they're renamed as well. Otherwise, whenin_hierarchy=False, only symbols that refers toOrange.eat() are renamed.

👋🏽
Let's try to move with this one too!
This seems to be an easy conflict to handle.

Hi@diraol, thank you for looking into these PRs, I've updated this one against the latest develop and addressed the merge conflicts.