go-timezone | Timezone utility for Go | Date Time Utils library

IANA timezones are available on most OSes (*). The Go standard library ships it as well:

This is a known issue with cpython on windows. The error occurs when black tries to run multiple workers on >60 core machines because the default number of process workers given by os.cpu_count() breaks some other windows limit (number of waiting processes? I'm not quite sure). Black >=19.10b0 has a fix for this, so try updating the version of black in your pre-commit config if you can?

• Python bug report: https://bugs.python.org/issue26903
• Fix applied by this PR in black: https://github.com/psf/black/pull/838

You're doing it the right way.

You're worried about the timezone offset changing (as with DST) in between the time you record the Location and when you do the computation. But a timezone (represented by a name like "America/Chicago") isn't just an offset, it's a set of rules for computing the local time at any point in history. So it will do the right thing regardless of when you happened to record the timezone name.

A few other notes on the code you posted:

• You probably want to make LocationHours unique on just location and weekeday, unless you're purposely trying to allow multiple opening hours for the same location on the same weekday.

• Your is_dt_within_location_hours() is fairly inefficient. You don't need to fetch all the LocationHours objects and re-compute the weekday each time. Instead, first compute the local time, then filter location.hours to only include the LocationHours objects on that weekday.

By looking at the log file, I have identified it was issue with requirement.txt pycurl. It was not getting installed properly.