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.

Sign up for GitHub

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

Jump to bottom

consider using keyring functionality to store API key #26

Open
nilsnolde opened this issue Nov 21, 2018 · 2 comments
Open

consider using keyring functionality to store API key #26

nilsnolde opened this issue Nov 21, 2018 · 2 comments

Comments

@nilsnolde
Copy link
Contributor

https://alexwlchan.net/2016/11/you-should-use-keyring/
@nilsnolde nilsnolde self-assigned this Nov 21, 2018
@aoles
Copy link
Member

aoles commented Nov 21, 2018 •
edited

I've been using keyring with the R client from the very beginning, but discovered that there are often issues with deployment so I'm actually considering moving away from it, see GIScience/openrouteservice-r#34. In fact, the dependence on keyring is the reason why the builds fail on Travis at the moment. Hopefully the implementation of keyring in Python is better :)

@nilsnolde
Copy link
Contributor Author

ok, thx for sharing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aoles @nilsnolde