Skip to content

Pop-up to install refactoring library appears when extensions invoke the rename provider, continues to appear after clicking "No" #15831

@rjzupkoii

Description

@rjzupkoii

Environment data

  • VS Code version: Version 1.55.0
  • Extension version: v2021.3.680753044
  • OS and version: Windows 10 Pro (20H2)
  • Python version (& distribution if applicable, e.g. Anaconda): 3.8.3 32-bit
  • Type of virtual environment used: N/A
  • Relevant/affected Python packages and their versions: XXX
  • Relevant/affected Python-related VS Code extensions and their versions: XXX
  • Value of the python.languageServer setting: Jedi

Other Extensions

  • Code Spell Checker (v1.10.2) with cSpell.fixSpellingWithRenameProvider set to true

Expected behaviour

When extensions use the rename provider to edit the source file (ex., to correct spelling errors in comments or strings), I should not be prompted to install the refactoring library "rope". If I decline to install the refactoring library, I should not be prompted to do so for the remainder of my session (resuming no means of disabling the prompt).

Actual behaviour

Prompt appears in lower right corner of screen asking if I wish to install the refactoring library "rope", clicking "No" dismisses the dialog but it reappears when correcting another spelling error. Rope was uninstalled due to a similar contextual error occurring see python-rope/rope#338

Steps to reproduce:

  1. Create a new Python file
  2. Enter a comment or string with a spelling error:
# Spelling error: vlaue
test = 'Spelling error: vlaue'
  1. Use Code Spell Checker to correct the spelling errors (i.e., select "Value" from the list)
  2. Prompt to install "rope" appears in lower right corner of screen (see below)

Install prompt for the rope refactoring library

Work arounds

The Code Spell Checker has the setting cSpell.fixSpellingWithRenameProvider, which when set to false prevents this error from occuring.

Logs

No logs are generated.

Metadata

Metadata

Labels

area-intellisenseLSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.bugIssue identified by VS Code Team member as probable bugverifiedVerification succeeded

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions