Skip to content
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

Add cache_path as a parameter to prompt_for_user_token() #167

Closed
jessejoe opened this issue Mar 2, 2017 · 0 comments
Closed

Add cache_path as a parameter to prompt_for_user_token() #167

jessejoe opened this issue Mar 2, 2017 · 0 comments

Comments

@jessejoe
Copy link
Contributor

@jessejoe jessejoe commented Mar 2, 2017

Currently prompt_for_user_token() sets cache_path to .cache-username under the user's current directory. This is problematic when using prompt_for_user_token() in other scripts since it will be looking for/creating .cache-username files in whatever directory the user happens to be in. This causes the user to have to re-authenticate and have duplicate files all over.

prompt_for_user_token() should allow the caller to set the cache_path or possibly even default to creating it inside the user's $HOME.

I'm happy to submit a PR for these if either seem like a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.