Humanized Opening Hours is a Python 3 module allowing a simple usage of the opening_hours fields used in OpenStreetMap.
Any pull request (following PEP-8) is more than welcome!
>>> import humanized_opening_hours as hoh
>>> field = "Mo-Fr 06:00-21:00; Sa,Su 08:00-12:00"
>>> oh = hoh.HumanizedOpeningHours(field)
>>> oh.is_open()
True
>>> oh.next_change()
datetime.datetime(2017, 12, 24, 12, 0)
>>> print(oh.render().plaintext_week_description())
"""
Monday: 06:00 - 21:00
Tuesday: 06:00 - 21:00
Wednesday: 06:00 - 21:00
Thursday: 06:00 - 21:00
Friday: 06:00 - 21:00
Saturday: 08:00 - 12:00
Sunday: 08:00 - 12:00
"""
This module is still in development and bugs may occur. If you discover one, please create an issue.
This library is so small, you can include it directly into your project. Also, it is available on PyPi.
$ pip3 install osm-humanized-opening-hours
The only mandatory argument to give to the constructor is the field, which must be a string.
>>> import humanized_opening_hours as hoh
>>> field = "Mo-Fr 06:00-21:00; Sa,Su 07:00-21:00"
>>>
>>> oh = hoh.OHParser(field)
>>> oh.is_open()
True
# To know if the facility is open at the present time. Returns a boolean. Can take a datetime.datetime moment to check for another time.
>>> oh.is_open()
True
# To know at which time the facility status (open / closed) will change. Returns a datetime.datetime object.
# Can take a datetime.datetime moment to check for another time.
# If we are on December 24 before 21:00 / 09:00PM...
>>> oh.next_change()
datetime.datetime(2017, 12, 24, 21, 0, tzinfo=<UTC>)
You can get a sanitized version of the field given to the constructor with the sanitize staticmethod or the sanitized_field attribute.
>>> field = "mo-su 0930-2000;jan off"
>>> print(hoh.OHParser.sanitize(field))
"Mo-Su 09:30-20:00; Jan off"
If you try to parse a field which is invalid or contains a pattern which is not supported, an humanized_opening_hours.exceptions.ParseError
(inheriting from humanized_opening_hours.exceptions.HOHError
) will be raised.
If the field contains a period which spans over midnight (like Mo-Fr 20:00-02:00
), a humanized_opening_hours.exceptions.SpanOverMidnight
exception (also inheriting from HOHError
) will be raised, because this is not supported yet.
If the field contains solar hours, here is how to deal with them.
First of all, you can easily know if you need to set them by checking the OHParser.needs_solar_hours_setting
variable.
If one of its values is True
, you need to set them in the solar_hours
dict with datetime.time
objects.
For example, if you know that the sunrise is at 08:00 and the sunset at 20:00, you can do this:
oh.solar_hours["sunrise"] = datetime.time(8, 0)
oh.solar_hours["sunset"] = datetime.time(20, 0)
If you try to do something with a field requiring setting without setting it, you will get a "SolarHoursNotSetError".
Attention, except if the facility is on the equator, this setting will be valid only for a short period.
The HOHRenderer
class allows you to get various representations of the schedules.
Its init method takes an OHParser object in argument, and two optional arguments:
universal
(bool) : allows to have human-readable descriptions without having to parse the solar hours (True default).locale_name
(str) : the language to use ("en" default), which can be changed with theset_locale()
method.
It has several methods to retrieve useful informations.
This object can also be created from an OHParser instance with its render()
method.
ohr = oh.render(universal=False)
Shorter, you can get it directly from a field with the render_field()
function.
ohr = hoh.render_field(field, universal=False)
Returns a list of the available locales (strings).
Allows to set a new locale for rendering. Takes a single argument: the locale_name.
Returns a dict of lists with the names of months and weekdays in the current locale.
Example:
>>> ohr.get_human_names()
{
'months': [
'January', 'February', 'March',
'April', 'May', 'June', 'July',
'August', 'September', 'October',
'November', 'December'
],
'days': [
'Monday', 'Tuesday', 'Wednesday',
'Thursday', 'Friday', 'Saturday',
'Sunday'
]
}
Returns a humanized delay before the next change in opening status.
>>> ohr.humanized_time_before_next_change()
"in 3 hours"
>>> ohr.humanized_time_before_next_change(word=False)
"3 hours"
Returns a plaintext description of the schedules of a week.
This method takes either a datetime.date
object or a list of datetime.date
objects.
In the first case, it is converted into a list of the days in the same week.
It can also take no parameter, so the described week will be the current one.
>>> ohr.plaintext_week_description()
"""
Monday: 08:00 - 19:00
Tuesday: 08:00 - 19:00
Wednesday: 08:00 - 19:00
Thursday: 08:00 - 19:00
Friday: 08:00 - 19:00
Saturday: 08:00 - 12:00
Sunday: closed
"""
Apart the main HumanizedOpeningHours class, HOH provides four other objects:
Day
: a weekday, or public or schoold holidays;Period
: a period with twoMoment
objects : a beginning and an end;MomentKind
: the kind of a period;Moment
: a moment in time, which can be a beginning or an end of a period.
Attributes:
periods
(list) : a list ofPeriod
objects included in this day;date
(datetime.date) : the date of the day;is_PH
(bool) : True if the day is a public holiday;is_SH
(bool) : True if the day is a school holiday.
# To know whether there is / are opening period(s) in this day.
>>> day.opens_today()
True
You can get a Day in two ways. Firstly with the get_day()
method of OHParser, which takes a datetime.date
object.
You can also use slicing with datetime.date
object(s). It also supports stepping (with an integer).
>>> oh[datetime.date.today()]
'<Day 'Mo' (2 periods)>'
>>> oh[datetime.date(2018, 1, 1):datetime.date(2018, 1, 3)]
['<Day 'Mo' (2 periods)>', '<Day 'Tu' (2 periods)>', '<Day 'We' (2 periods)>']
Attributes:
beginning
(Moment object) : the beginning of the period;end
(Moment object) : the end of the period.
# To know if a period contains a solar hour, use the `is_variable()` method.
>>> period.is_variable()
datetime.timedelta(0, 10800)
# Know if a datetime.time object is between the beginning and the end of this period (i.e. it is open at this time).
>>> moment = datetime.time(18, 30)
>>> moment in period
True
A simple Enum with the following values:
NORMAL
;SUNRISE
;SUNSET
;DAWN
;DUSK
.
Attributes:
kind
(MomentKind) : the kind of this moment;
# Gets a datetime.time object (localized on UTC), or None if the moment is variable.
>>> moment.time()
datetime.time(18, 30, tzinfo=<UTC>)
Here are the field formats officialy supported and tested (examples).
24/7
Mo 10:00-20:00
Mo-Fr 10:00-20:00
Sa,Su 10:00-20:00
Su,PH off # or "closed"
10:00-20:00
sunrise-sunset # or "dawn" / "dusk"
(sunrise+01:00)-20:00
Jan 10:00-20:00
Jan-Feb 10:00-20:00
Jan,Dec 10:00-20:00
Jan Mo 10:00-20:00
Jan,Feb Mo 10:00-20:00
Jan-Feb Mo 10:00-20:00
Jan Mo-Fr 10:00-20:00
Jan,Feb Mo-Fr 10:00-20:00
Jan-Feb Mo-Fr 10:00-20:00
SH Mo 10:00-20:00
SH Mo-Fr 10:00-20:00
The following formats are NOT supported yet and their parsing will raise a ParseError.
20:00-02:00 # Span over midnight.
years
weeks
easter 10:00-20:00
Su[1] 10:00-20:00
SH,PH Mo-Fr 10:00-20:00
SH,PH Mo-Fr,Su 10:00-20:00
Jan-Feb,Aug Mo-Fr,Su 10:00-20:00
HOH uses the module Lark (with the LALR parser) to parse the fields. It takes about 0.0007 seconds to parse a basic field, 0.08 seconds to parse a hundred, and 0.5 for a thousand.
This module requires the following modules, which can be installed with pip3
.
lark-parser
pytz
babel
This module is published under the AGPLv3 license, the terms of which can be found in the LICENCE file.