-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
7.1.2 Update to asyncclick breaks github install of python-kasa #106
Comments
Could you please add the complete stack trace to the description? The poetry.lock should actually take precedence over pyproject.toml, that's the reason for the locking after all. |
Here is trace from running kasa at the command line:
|
And here is information provided during the python-kasa install, which installs asyncclick 7.1.2.1. This is where the problem seems to arise (and may be down to my misunderstanding how to use pip to do a git install).
|
Considering that it works with 7.0.9, it feels like this were a regression in asyncclick. I tried to do some git log analysis to see what could have caused it, but couldn't find anything useful. https://github.com/python-trio/asyncclick/blob/master/src/click/_winconsole.py is the file and it has no Anyway, this is not really something we can handle in this repository, so could you please open a new issue in asyncclick's repository describing what you described here, and let's hope it'll get fixed at some point? |
Will do - I'll close this when I file the new issue. |
Solved, please upgrade asyncclick to 7.1.2.2. |
Closed by python-trio/asyncclick#8. |
I've just installed the latest master
python-kasa
in clean environment on Windows usingpip install git+https://github.com/python-kasa/python-kasa.git
, which installs asyncclick 7.1.2 (consistent with pyproject.toml (^7
), but not poetry.lock (7.0.9
)).When I run kasa, I get the following import error:
As a short term fix, I've reverted to 7.0.9 by using
pip install asyncclick==7.0.9
.Isssue #8 for asyncclick covers the same problem - I'm not sure that the fix is relevant though.
I presume this is due to pyproject.toml taking precedence over poetry.lock - as I haven't got to grips with recent changes to installation methods, I don't have any useful suggestions for a proper fix (unless it is as simple as updating pyproject.toml?).
The text was updated successfully, but these errors were encountered: