Ref Issue 21.

The .load_forecast() method is currently converting the datetime argument to seconds since the epoch in local time, which has the effect of making it an "aware" datetime. That is, it imbues the datetime with statefulness w.r.t. location that it doesn't necessarily have already, if it's passed as a naïve datetime (i.e. "5 o'clock somewhere", not necessarily "5 o'clock in Greenwich.")

Technically, the issue is that time.mktime() takes an argument in local time (i.e. the locale of my laptop) and converts to seconds since the epoch (docs). In the API though, they expect a naïve datetime, unless timezone is specified. From the API docs:

For the latter format, if no timezone is present, local time (at the provided latitude and longitude) is assumed. (This string format is a subset of ISO 8601 time. An as example, 2013-05-06T12:00:00-0400.)

My thought was, that in order to make the wrapper as thin as possible, that it should behave in the same way. Instead of using mktime(), it should use isoformat().

In [1]: %paste
import time
import datetime
from delorean import Delorean

## -- End pasted text --

In [2]: d = datetime.datetime(2015, 4, 11, 2, 45)  # initialized without any tzinfo

In [3]: d.isoformat()  # this format has no tzinfo, is naïvely unaware of location
Out[3]: '2015-04-11T02:45:00'

In [4]: ep = time.mktime(d.timetuple())

In [5]: ep  # this number is only associated with datetime(2015, 4, 11, 2, 45) in the sense of GMT-04:00 (I'm in New York.) So it's no longer naïve to location.
Out[5]: 1428734700.0

In [6]: dl = Delorean(d, timezone="US/Mountain")  # use delorean to create a timezone-aware datetime.datetime

In [7]: dl.datetime  
Out[7]: datetime.datetime(2015, 4, 11, 2, 45, tzinfo=<DstTzInfo 'US/Mountain' MDT-1 day, 18:00:00 DST>)

In [8]: dl.datetime.isoformat()  # in this case timezone info would be passed on to the API.
Out[8]: '2015-04-11T02:45:00-06:00'

Under the Docs for v2 is an lang= Option. It would be nice to see this implemented as something like this:

foo = forecastio.load_forecast(key, latitude, longitude, lang="en")

This was added to the API on 29 May 2014: https://developer.forecast.io/docs/v2#options

Currently this is not working. Are there any quick workarounds?

entered the command sudo pip install python-forecastio in to terminal and it come out with this: (yes i do have PIP)

pi@raspberrypi ~ $ sudo pip install python-forecastio Downloading/unpacking python-forecastio Running setup.py egg_info for package python-forecastio

Downloading/unpacking requests>=1.6 (from python-forecastio) Running setup.py egg_info for package requests

Downloading/unpacking responses (from python-forecastio) Running setup.py egg_info for package responses No handlers could be found for logger "main"

Downloading/unpacking cookies (from responses->python-forecastio) Running setup.py egg_info for package cookies

Requirement already satisfied (use --upgrade to upgrade): six in /usr/local/lib/python2.7/dist-packages (from responses->python-forecastio) Downloading/unpacking mock (from responses->python-forecastio) Running setup.py egg_info for package mock mock requires setuptools>=17.1. Aborting installation Complete output from command python setup.py egg_info: mock requires setuptools>=17.1. Aborting installation

Command python setup.py egg_info failed with error code 1 in /home/pi/build/mock Storing complete log in /root/.pip/pip.log

The way times (and dates) are handled is inconsistent and needs an overhaul.

Times are represented using a mix Python datetime objects and unix timestamps. This needs to be standardised to Python objects. Also, when using times, it is not clear what time zone the API expects. Is it local time or the time at the forecast location? This all needs to be cleaned up and documented.

One option (this is the approach that Forecast.io has taken) is to always use UTC time.

This is probably my prefered approach as it will standardise the representation of time within the wrapper and also between the wrapper and the HTTP API.

Added the ability to control the language parameter for Dark Sky. This is needed for my modifications for the Home Assistant Dark Sky Sensor where I want to have german weather forecasts :-) So it would be great if you could release a new version of your library and I'll raise the version of the dependency accordingly in order to finish my Home Assistant pull request.

Thanks!

As per today's announcement:

The API endpoint has changed from https://api.forecast.io/ to https://api.darksky.net/. The previous endpoint will continue to work for the foreseeable future, but please change your software as soon as possible.

Hello,

Thanks for creating this wrapper! I've added the ability for the user to enter a simple string that can be geocoded using Geopy instead of having to pass in an explicit lat and long. Adding this feature of course adds another dependency.

I've also updated example.py to demonstrate how this would be used, and updated the test suite, however since it doesn't appear to actually call load_forecast, it's not really getting tested.

Hey,

This is super useful and I love it. Had to install manually as pip install couldn't find a matching package. When I searched for it, it recommended python-forcastio (<--that's not a typo), but said there was no matching version for pypi to install.

I'm running into an issue, whether I use forecastio with 2.7 or 3.4, where I'm getting the following error:

AttributeError: "'Forecast' object has no attribute 'unicode'"

Not sure what I'm doing wrong or if this is a legit bug. Thanks in advance!

Maybe you can have a look, not sure if it is related to your package, but other modules did install.

Install packages failed: Error occurred when installing package python-forecastio. 

The following command was executed:

packaging_tool.py install --build-dir /private/var/folders/gj/84mj91y514z79t19xfc8t8sr0000gn/T/pycharm-packaging5452297355347498062.tmp --user python-forecastio

The error output of the command:

Traceback (most recent call last):
  File "/Applications/PyCharm.app/helpers/packaging_tool.py", line 56, in do_install
    import pip
  File "/usr/local/Cellar/python3/3.4.1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/pip/__init__.py", line 10, in <module>
    from pip.util import get_installed_distributions, get_prog
  File "/usr/local/Cellar/python3/3.4.1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/pip/util.py", line 18, in <module>
    from pip._vendor.distlib import version
  File "/usr/local/Cellar/python3/3.4.1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/pip/_vendor/distlib/version.py", line 14, in <module>
    from .compat import string_types
  File "/usr/local/Cellar/python3/3.4.1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/pip/_vendor/distlib/compat.py", line 66, in <module>
    from urllib.request import (urlopen, urlretrieve, Request, url2pathname,
ImportError: cannot import name 'HTTPSHandler'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Applications/PyCharm.app/helpers/packaging_tool.py", line 125, in main
    retcode = do_install(pkgs)
  File "/Applications/PyCharm.app/helpers/packaging_tool.py", line 58, in do_install
    error_no_pip()
  File "/Applications/PyCharm.app/helpers/packaging_tool.py", line 36, in error_no_pip
    tb = sys.exc_traceback
AttributeError: 'module' object has no attribute 'exc_traceback'

Forecast.io has a beta option to view irradiance data. I'd like be able to use this, so I added the parameter solar to the method: forecastio.api.load_forecast

The way to view this data would be:

import forecastio from forecastio.utils import PropertyUnavailable forecast = forecastio.load_forecast('%^&!@#(@&#@()$#',37.8267,-122.423, solar=True) byHour = forecast.hourly() for hourlyData in byHour.data: try: print hourlyData.time, hourlyData.solar except PropertyUnavailable: pass

This irradiance data is only available during daylight hours, which is why you we need to skip occasionally.

I am trying to run a basic Python example from your GitHub repo for which I need an API key. Your website says "We are no longer accepting new signups." Does this mean it is no longer possible to obtain an API key?

I've got a script built to report daily data forecasts, but sometimes I get the forecastio.utils.PropertyUnavailable error. I understand that this means there is no data for the particular forecast item I'm looking for. What I'm asking is how do I handle for these errors? This error is causing my script not to finish retrieving the forecast because of this error.

Traceback (most recent call last):
  File "/home/user/.local/lib/python3.6/site-packages/forecastio/models.py", line 103, in __getattr__
    return self.d[name]
KeyError: 'precipType'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "DarkSky.py", line 100, in <module>
    main()
  File "DarkSky.py", line 97, in main
    getDaily(forecast_data)
  File "DarkSky.py", line 70, in getDaily
    'Precip_Type' : i.precipType,
  File "/home/user/.local/lib/python3.6/site-packages/forecastio/models.py", line 107, in __getattr__
    " or is not available for this forecast".format(name)
forecastio.utils.PropertyUnavailable: Property 'precipType' is not valid or is not available for this forecast

I'd be fine with being able to say something like: 'Precipitation Type: none or no precipitation type data exists for this forecast'

The problem is I can't figure out how to handle for this error.

I've tried

exception KeyError:
    print('No data exists for this forecast variable')

and

exception forecastio.utils.PropertyUnavailable:
    print('No data exists for this forecast variable')

But neither of these work. I noticed in the traceback that this ultimately results from a KeyError exception, but using this as an Exception raise doesn't work.

Can anyone help with how to handle for these errors? Thanks

What is the correct way to create a Flag Object so that I can then proceed to gather the following data:

nearest-station required The distance to the nearest weather station that contributed data to this response. Note, however, that many other stations may have also been used; this value is primarily for debugging purposes. This property's value is in miles (if US units are selected) or kilometers (if SI units are selected). sources required This property contains an array of IDs for each data source utilized in servicing this request. units required Indicates the units which were used for the data in this request.

I have been successful at creating DataPoint Objects, DataBlock Objects, and Alerts Arrays; but so far I have been unable to create a flag object. I cant find any documentation as to how to properly create one, I have been trying this:

forecast = forecastio.load_forecast(api_key, lat, lng)
ws = forecast.flags()

but it yields:

AttributeError: 'Forecast' object has no attribute 'flags'

I need it to find out from what weather station is being used.

Thanks!!!

when a call to Forecast update() is made, the alerts don't seem to get updated

in init you have

        self._alerts = []
        for alertJSON in self.json.get('alerts', []):
            self._alerts.append(Alert(alertJSON))

but in update nothing happens to _alerts

is that on purpose?

I only need to get forecast.currently(). So, I would like to exclude getting the minutely, hourly, daily, alerts, and flags data (to reduce latency).

The Dark Sky documentation supports an exclude parameter. Does the python-forecast.io library accept this parameter?