Skip to content
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

The Rename Method refactoring is allowed in the overridden method. #746

Open
researcher175 opened this issue Jan 15, 2024 · 0 comments
Open
Labels
bug Unexpected or incorrect user-visible behavior rename-refactor

Comments

@researcher175
Copy link

The method that overrides the superclass method receives the refactoring without warning the user that there is a superclass method.
It would be nice if Rope could emit a warning in this case.

Steps to reproduce the behavior:

  1. Code before refactoring:
class MyList(list):

    def count(self, strg, case_sensitive=False, *args, **kwargs):
        return super(MyList, self).count(strg, *args, **kwargs)
  1. Apply the Rename Method in MyList.count().
@researcher175 researcher175 added the bug Unexpected or incorrect user-visible behavior label Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected or incorrect user-visible behavior rename-refactor
Projects
None yet
Development

No branches or pull requests

2 participants