We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This will affect version 3.0 as it is a breaking change in the library API.
We need to normalise the weather retrieval functions to the naming pattern:
where "forecast_granularity" can be either "3h" or "daily"
The text was updated successfully, but these errors were encountered:
# OLD SIGNATURE # NEW SIGNATURE three_hours_forecast(self, name) --> forecast_at_place(self, name, "3h", [limit]) daily_forecast(self, name, limit=None) --> forecast_at_place(self, name, "daily", [limit]) three_hours_forecast_at_coords(self, lat, lon) --> forecast_at_coords(self, lat, lon, "3h", [limit]) daily_forecast_at_coords(self, lat, lon, limit=None) --> forecast_at_coords(self, lat, lon, "daily", [limit]) three_hours_forecast_at_id(self, id) --> forecast_at_id(self, id, "3h", [limit]) daily_forecast_at_id(self, id, limit=None) --> forecast_at_id(self, id, "daily", [limit])
Sorry, something went wrong.
Started #42: three_hours_forecast + daily_forecast = forecast_at_place
06a96c5
Started #42: three_hours_forecast + daily_forecast = forecast_at_coords
3331dec
Completed #42: three_hours_forecast + daily_forecast = forecast_at_id
06e4eb8
csparpa
No branches or pull requests
This will affect version 3.0 as it is a breaking change in the library API.
We need to normalise the weather retrieval functions to the naming pattern:
where "forecast_granularity" can be either "3h" or "daily"
The text was updated successfully, but these errors were encountered: