-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Error on Ubuntu with Python 3.7 #229
Comments
This is happening on unimport-0.9.6 btw, which is the same version that seems to work fine on 3.10 and in my environment. |
Thanks for letting me know, I'll work on it as soon as possible. |
For now, to solve your problem, I can recommend you to use pre-commit, where you can define all your linters in one place and run them with Github action. https://pre-commit.com/ |
Thank you! I could also just put the linter check in its own action which uses 3.10, I might do that since it needs the fewest changes to my workflow. |
I think no need, you found a nice bug, Unimport has never been used before with Github action, if you wait a few days I will fix this issue. |
I will test it. |
Thanks for letting me know, I tested it, you can use it with GitHub action using version 0.10.0, or directly unimport.yml
Let's check -> https://unimport.hakancelik.dev/#use-with-github-action |
Hey @hakancelikdev, in my project another user has report experiencing a similar issue locally on a Mac:
Do you think this is the same bug? Do you know of a workaround that could avoid this? Thank you! |
@ajyoon Which version of unimport do you use? |
We're using a plain |
Yeah I just confirmed I'm running |
Running through the pre-commit framework seems to have solved the issue for us. It's possible the the user was getting an old version of unimport from before this fix. |
I recently changed my project's CI from using Python 3.10 to 3.7 and unimport started failing with this error:
I can't reproduce this on my local machine (Arch Linux with Python 3.7.13), but you can see detailed environment info on the build here.
The text was updated successfully, but these errors were encountered: