-
Notifications
You must be signed in to change notification settings - Fork 2
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
Doesn't work with radon 6.0.1 #5
Comments
Managed to reproduce this on Windows 11, Python 3.11.4, VS Code 1.78.2. Installing 5.1 fixes the issue. |
I suppose it is this line causing the version check confusion: python-radon/src/RadonProvider.ts Line 78 in af0b4c9
if (major < 5 || minor < 1) {
throw new UnsupportedVersionException("You need at least python radon version 5.1 installed. Try pip install \"radon>=5.1\".");
} Should fix itself with a radon version that has the minor version >= 1. But I think the version check should be fixed. |
Fix for Issue cdein#5 Fix version check to allow major versions higher than 5 and with minor versions lower than 1 (like 6.0.1)
Still, an issue as of today since the fix was merged in July of 2023( as you can see from above) but the last released in the vs code store was: Last released |
Still facing this issue today. @cdein, any plans on releasing the fix on the vscode marketplace any time soon? I'd like to promote the use of this in my company as it's a really useful tool... |
I too would like to see this released. In the meantime you can actually create a simple wrapper script to intercept a call to the binary with the '-v' argument and then perform a proper check and just return 5.2 if the version really is >=5.1. |
Still doesn't work. Getting into vscode-radon-linter. |
Tried to use the extension with the latest radon package (6.0.1), but the extension kept spamming
Also cyclomatic complexity wasn't showing in the .py files.
After installing radon version 5.1 the issue resolved itself.
Windows 10 Pro 10.0.19045
VS Code 1.78.2
Python 3.10.11
The text was updated successfully, but these errors were encountered: