-
Notifications
You must be signed in to change notification settings - Fork 262
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
KeyError: "name='sid', domain=None, path=None" #324
Comments
it is a known error in gimme-aws-creds v 2.4.0 so you will try to run something like then you may try to run and you will get an error message like and you will scratch your head because 3.10 > 3.7 but then your head will hurt because "3.10" < "3.7" anyways this was my afternoon today |
It has nothing to do with string comparisons in requirements (that issue was fixed in pip back in 2019). The reason is that there's no winrt release for 3.10, see microsoft/xlang#763 |
Any idea how we can work around this? Is it just to downgrade your python version from 3.10 to 3.9? |
yes, you can only install it on python 3.9 (or lower) until winrt is upgraded to 3.10 |
Thank you for your reply, that worked for me. |
|
I already downgrade my python to 3.9 and even with that change I have the same issue. Any help of what I can do? |
Having same issues with python 3.10 running on Macos. gimme-aws-creds version = 2.4.4 |
I have python 3.9.13 and gimme creds 2.4.4 , when I use the command "gimme-aws-creds" I see my terminal is hanging at "Using password from keyring" and does not respond. Can anyone help me on how to resolve this please? |
Team, per microsoft/xlang#763 are there plans to replace winrt with https://pypi.org/project/winsdk/ in gimme-aws-creds in the near future? |
Finally, Install gimme creds without any error on my system. It worked for me !!!. |
New installation of gimme-aws-creds v2.4.0 on Windows 10. Python version 3.10.0. After entering Okta credentials, a bunch of errors are displayed ending with KeyError: "name='sid', domain=None, path=None".
Anonymized output and config file attached.
okta_aws_login_config.txt
error-output.txt
The text was updated successfully, but these errors were encountered: