Up to [cvs.NetBSD.org] / pkgsrc / time / py-tzlocal
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
py-tzlocal: updated to 5.3.1 5.3.1 (2025-03-05) - Now only warns bout /etc/timezone if it is actually conflicting with other timezone configurations.
py-tzlocal: updated to 5.3 5.3 (2025-02-13) - Now supports Python 3.9 to 3.13, and no longer requires backports.zoneinfo. - Debian is for some reason removing support for /etc/timezone, which is bad, because that's the only place where the timezone is stated in plain text, and what's worse, they don't delete it. So we can't trust it now, so when we have multiple configs, we are forced to just ignore it. - Attempts to return a ZoneInfo object also for UTC.
py-tzlocal: updated to 5.2 5.2 (2023-10-22) - Added a pre-commit config - Updated python versions [hugovk] - Added type hints for the public functions - Moved to using pyproject.toml for project config.
py-tzlocal: updated to 5.1 5.1 (2023-10-04) ---------------- - The Unicode data doesn't change tz names when IANA does, so what is current in IANA is treated as an alias in Unicode data. This version handles that.
py-tzlocal: update to 5.0.1. 5.0.1 (2023-05-15) ------------------ - The logging info under windows made it look like it looked up the registry info even when you had a TZ environment, but it doesn't actually do that. - Improved the handling of loggers. 5.0 (2023-05-14) ---------------- - Fixed a bug in the new assert_tz_offset method. 5.0b2 (2023-04-11) ------------------ - Change how the system offset is calculated to deal with non-DST temporary changes, such as Ramadan time in Morocco. - Change the default to only warn when the timezone offset and system offset disagree (but still not even warn if TZ is set) - Add the assert_tz_offset() method to the top level for those who want to explicitly check and fail. 5.0b1 (2023-04-07) ------------------ - Removed the deprecation shim. 4.4b1 (2023-03-20) ------------------ - Added debug logging
py-tzlocal: update to 4.3. 4.3 (2023-03-18) ---------------- - Improved the error message when the ZoneInfo cannot be found - Don't error out because we find multiple possible timezones for a symlink. - More stable on Android/Termux with proot 4.2 (2022-04-02) ---------------- - If TZ environment variable is set to /etc/localhost, and that's a link to a zoneinfo file, then tzlocal will now find the timezone name, and not just return a localtime TZ object. 4.1 (2021-10-29) ---------------- - No changes from 4.1b1. 4.1b1 (2021-10-28) ------------------ - It turns out a lot of Linux distributions make the links between zoneinfo aliases backwards, so instead of linking GB to Europe/London it actually links the other way. When /etc/localtime then links to Europe/London, and you also have a config file saying Europe/London, the code that checks if /etc/localtime is a symlink ends up at GB instead of Europe/London and we get an error, as it thinks GB and Europe/London are different zones. So now we check the symlink of all timezones in the uniqueness test. We still return the name in the config file, though, so you would only get GB or Zulu returned as the time zone instead of Europe/London or UTC if your only configuration is the /etc/localtime symlink, as that's checked last, and tzlocal will return the first configuration found. - The above change also means that GMT and UTC are no longer seen as synonyms, as zoneinfo does not see them as synonyms. This might be controversial, but you just have to live with it. Pick one and stay with it. ;-) 4.0.2 (2021-10-26) ------------------ - Improved the error message when you had a conflict including a /etc/localtime symlink. 4.0.1 (2021-10-19) ------------------ - A long time bug in Ubuntu docker images seem to not get fixed, so I added a workaround. 4.0.1b1 (2021-10-18) -------------------- - Handle UCT and Zulu as synonyms for UTC, while treating GMT and UTC as different. 4.0 (2021-10-18) ---------------- - No changes. 4.0b5 (2021-10-18) ------------------ - Fixed a bug in the Windows DST support. 4.0b4 (2021-10-18) ------------------ - Added support for turning off DST in Windows. That only works in whole hour timezones, and honestly, if you need to turn off DST, you should just use UTC as a timezone. 4.0b3 (2021-10-08) ------------------ - Returning pytz_deprecation_shim zones to lower the surprise for pytz users. - The Windows OS environment variable 'TZ' will allow an override for setting the timezone. The override timezone will be asserted for timezone validity bit not compared against the systems timezone offset. This allows for overriding the timezone when running tests. - Dropped support for Windows 2000, XP and Vista, supports Windows 7, 8 and 10. 4.0b2 (2021-09-26) ------------------ - Big refactor; Implemented get_localzone_name() functions. - Adding a Windows OS environment variable 'TZ' will allow an override for setting the timezone (also see 4.0b3). 4.0b1 (2021-08-21) ------------------ - Now finds and compares all the configs (under Unix-like systems) and tells you what files it found and how they conflict. This should make it a lot easier to figure out what goes wrong. 3.0 (2021-08-13) ---------------- - Modernized the packaging, moving to setup.cfg etc. - Handles if the text config files incorrectly is a TZ file. (revanSZ) 3.0b1 (2020-09-21) ------------------ - Dropped Python 2 support - Switched timezone provider from pytz to zoneinfo (PEP 615)
time: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes
time: Remove SHA1 hashes for distfiles
py-tzlocal: updated to 2.1 2.1: - No changes. 2.1b1: - The is_dst flag is wrong for Europe/Dublin on some Unix releases. I changed to another way of determining if DST is in effect or not. - Added support for Python 3.7 and 3.8. Dropped 3.5 although it still works.
py-tzlocal: updated to 2.0.0 2.0.0: Major differences since 1.5.1 - When no time zone configuration can be find, tzlocal now return UTC. This is a major difference from 1.x, where an exception would be raised. This change is because Docker images often have no configuration at all, and the unix utilities will then default to UTC, so we follow that. - If tzlocal on Unix finds a timezone name in a /etc config file, then tzlocal now verifies that the timezone it fouds has the same offset as the local computer is configured with. If it doesn't, something is configured incorrectly. - Get timezone via Termux `getprop` wrapper on Android. It's not officially supported because we can't test it, but at least we make an effort. Minor differences and bug fixes - Skip comment lines when parsing /etc/timezone. - Don't load timezone from current directory. - Now verifies that the config files actually contain something before reading them. - Got rid of a BytesWarning - Now handles if config file paths exists, but are directories. - Moved tests out from distributions - Support wheels
py-tzlocal: updated to 1.5.1 1.5.1: - 1.5 had a bug that slipped through testing, fixed that, increased test coverage. 1.5: - No longer treats macOS as special, but as a unix. - get_windows_info.py is renamed to update_windows_mappings.py - Windows mappings now also contain mappings from deprecated zoneinfo names. (Preston-Landers, regebro)
Changes 1.4: I use MIT on my other projects, so relicensing. Dropping support for Python versions nobody uses (2.5, 3.1, 3.2), adding 3.6 Python 3.1 and 3.2 still works, 2.5 has been broken for some time. Ayalash’s OS X fix didn’t work on Python 2.7, fixed that.
Add SHA512 digests for distfiles for time category Problems found with mismatching existing digests for: distfiles/asclock-classic-1.0.tar.gz distfiles/asclock-gtk-2.1.10beta.tar.gz distfiles/asclock-xlib-2.0.11.tar.gz distfiles/emiclock-2.0.2.tar.gz Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
Import py34-tzlocal-1.1.2 as time/py-tzlocal. This Python module returns a tzinfo object with the local timezone information under Unix and Win-32. It requires pytz, and returns pytz tzinfo objects. This module attempts to fix a glaring hole in pytz, that there is no way to get the local timezone information, unless you know the zoneinfo name, and under several Linux distros that's hard or impossible to figure out. Also, with Windows different timezone system using pytz isn't of much use unless you separately configure the zoneinfo timezone name. With tzlocal you only need to call get_localzone() and you will get a tzinfo object with the local time zone info. On some Unices you will still not get to know what the timezone name is, but you don't need that when you have the tzinfo file. However, if the timezone name is readily available it will be used.