-
-
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
don't prompt to unlock keychain unless it's needed #208
Comments
I can't remember who told me they were encountering this, but I can't reproduce it on Fedora 31 using KDE. I'll need to figure out who encountered it and ask for more information about their environment. |
@duckinator I encountered it too, but even on non- You can get hints that something is trying to use the keyring, by putting some garbage in
I guess one could also use the kernel's audit capabilities or somesuch, to log accesses to that file. |
It looks like https://github.com/pypa/pep517/blob/master/pep517/envbuild.py#L92 is the last thing called before it happens, so I'm wondering if it's a pip thing.
|
Yes, it is:
|
Yeah, just found a plethora of pip issues about keyring support. Looks like there is consensus on making keyring opt-in but nobody actually implemented anything. |
We don't use If anyone encounters this again, please open a new issue for it. |
i suspect this automagically happens upon importing stuff from twine, but i'm not sure. if that is the case, we can just do a non-top-level import in
bork.pypi.upload(...)
.The text was updated successfully, but these errors were encountered: