-
Notifications
You must be signed in to change notification settings - Fork 28
Basic functionality for #5: Implement Text forecast #25
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
Basic functionality for #5: Implement Text forecast #25
Conversation
|
Test failures are due to the API key not being set. This is fine as it is a PR and Travis hides the key for security. Can you set the |
|
Recreated error with the following steps Getting the following error |
|
Can you write a quick usage example for this? See the current examples for inspiration. |
|
|
||
| # Create datapoint connection | ||
| #aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee | ||
| conn = datapoint.Manager(api_key="c4260d02-3133-488d-91bd-abf66150dbe9") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps this key should be here?
This is a first pass at adding support for the regional text forecast.
The idea is that this allows requesting the 'raw' text forecast - as you can see from the example this requires a bit of work on the user side to make usable. This leaves room for a more opinionated implementation to be added later.