Removing unused imports with "Optimize Imports" command does not work

[Cykooz]

Removing unused imports with "Optimize Imports" command does not work in case if:

• option "Use Import Optimizer" in Ruff plugin is enabled
• fixing unused imports disabled in .ruff.toml file:

[lint]
unfixable = ["F401"]

If I disable Ruff plugin, everything works fine. Unused imports will be removed with help "Optimize Imports" command.

[aleksey-orekhov]

To the devs: Thank you so very much for making this amazing and useful plugin! Hopefully this will be helpful:

I was able to reproduce this. There is a temporary workaround:

If you go into Settings->Tools->Ruff and check "Use Import Optimizer", the import optimizer appears to start working again.

I also observed that if you don't follow my advice above, and you leave the "Use Import Optimizer" box unchecked, you can still run "Optimize Imports" from the "Problems" pane. (It is next to the terminal window in my pycharm. Icon is an exclamation point with a circle around it.

I'm not sure why that checkbox is there or what it does. i.e. does it replace the JetBrains import optimizer with one from Ruff? After enabling the ruff logs, I now understand that the "Use Import Optimizer" checkbox causes the Ruff import optimizer to be used. If that is the case:

1. If the box is not checked, the build in JetBrains import optimizer should probably still run? (Or the checkbox text should be modified to warn that unchecking it will disable import optimization)

2. The ruff import optimizer should be the one used from the 'Problems' pane.

Hope that helps, and thanks again!

[anvishinc]

@aleksey-orekhov It seems there's a bug with the plugin where disabling the "Use Import Optimizer" feature also inadvertently disables the built-in import optimizer. As a result, when you enable it again, neither the built-in actions on save nor Ruff formatting work as expected. This issue is present in the 2025 version of PyCharm, and I've noticed that 5-10 of the most recent issues are addressing this same problem. I'm not sure if it's happening in the 2024 version though but some have mentioned similar issues even in that version