python-dateutil 2.9.0.post0__tar.gz → 4.0.0__tar.gz

{python-dateutil-2.9.0.post0 → python_dateutil-4.0.0}/.gitignore

@@ -21,6 +21,7 @@ src/dateutil/_version.py
 
 # Sphinx documentation
 docs/_build/
+docs/docs_venv
 
 # Timezone information
 tzdata*.tar.gz

{python-dateutil-2.9.0.post0 → python_dateutil-4.0.0}/AUTHORS.md

@@ -11,6 +11,7 @@ switch, and thus all their contributions are dual-licensed.
 
 ## Contributors (alphabetical order)
 
+- Aarni Koskela <akx@iki.fi> **D**
 - Adam Chainz <adam@MASKED>
 - Adrien Cossa <cossa@MASKED>
 - Alec Nikolas Reiter <alecreiter@MASKED>
@@ -59,14 +60,18 @@ switch, and thus all their contributions are dual-licensed.
 - Igor <mrigor83@MASKED>
 - Ionuț Ciocîrlan <jdxlark@MASKED>
 - Jacqueline Chen <jacqueline415@outlook.com> (gh: @jachen20) **D**
+- Jairo Llopis (gh: @yajo) **D**
 - Jake Chorley (gh: @jakec-github) **D**
 - Jakub Kulík (gh: @kulikjak) **D**
 - Jan Studený <jendas1@MASKED>
+- JAY (gh: @Jay1023CN) **D**
 - Jay Weisskopf <jay@jayschwa.net> (gh: @jayschwa) **D**
 - Jitesh <jitesh@MASKED>
 - John Purviance <jpurviance@MASKED> (gh @jpurviance) **D**
 - Jon Dufresne <jon.dufresne@MASKED> (gh: @jdufresne) **R**
 - Jonas Neubert <jonas@MASKED> (gh: @jonemo) **R**
+- Jordi Masip <jordi@MASKED> (gh: @masipcat)
+- Juan Arias <jdarias3@gmail.com> (gh: @jdarias3) **D**
 - Kevin Nguyen <kvn219@MASKED> **D**
 - Kirit Thadaka <kirit.thadaka@gmail.com> (gh: @kirit93) **D**
 - Kubilay Kocak <koobs@MASKED>
@@ -87,6 +92,7 @@ switch, and thus all their contributions are dual-licensed.
 - Nicholas Herrriot <Nicholas.Herriot@gmail.com> **D**
 - Nicolas Évrard (gh: @nicoe) **D**
 - Nick Smith <nick.smith@MASKED>
+- Nor.na (gh: @Master-Norna) **D**
 - Orson Adams <orson.network@MASKED> (gh: @parsethis) **D**
 - Paul Brown (gh: @pawl) **D**
 - Paul Dickson (gh @prdickson) **D**
@@ -99,6 +105,7 @@ switch, and thus all their contributions are dual-licensed.
 - Raymond Cha (gh: @weatherpattern) **D**
 - Ridhi Mahajan <ridhikmahajan@MASKED> **D**
 - Robin Henriksson Törnström <gh: @MrRawbin> **D**
+- Rowan Walsh (gh: @rowan-walsh) **D**
 - Roy Williams <rwilliams@MASKED>
 - Rustem Saiargaliev (gh: @amureki) **D**
 - Satyabrat Bhol <satyabrat35@MASKED> (gh: @Satyabrat35) **D**
@@ -116,6 +123,7 @@ switch, and thus all their contributions are dual-licensed.
 - Tomasz Kluczkowski (gh: @Tomasz-Kluczkowski) **D**
 - Tomi Pieviläinen <tomi.pievilainen@iki.fi>
 - Unrud <Unrud@MASKED> (gh: @unrud)
+- varun netrakar <varun@security.bugqore.com> (gh: @varun3257) **D**
 - Xavier Lapointe <lapointe.xavier@MASKED> (gh: @lapointexavier) **D**
 - X O <xo@MASKED>
 - Yaron de Leeuw <me@jarondl.net> (gh: @jarondl)
@@ -124,6 +132,7 @@ switch, and thus all their contributions are dual-licensed.
 - Zbigniew Jędrzejewski-Szmek <zbyszek@MASKED>
 - bachmann <bachmann.matt@MASKED>
 - bjv <brandon.vanvaerenbergh@MASKED> (@bjamesvERT)
+- friskysaga (gh: @kevinkt1) **D**
 - gl <gl@MASKED>
 - gfyoung <gfyoung17@gmail.com> **D**
 - Labrys <labrys.git@gmail.com> (gh: @labrys) **R**

{python-dateutil-2.9.0.post0 → python_dateutil-4.0.0}/CONTRIBUTING.md

@@ -33,7 +33,8 @@ To keep users abreast of the changes to the module and to give proper credit, `d
 - `feature`: A new feature, (e.g. a new function, method, attribute, etc)
 - `bugfix`: A fix to a bug
 - `doc`: A change to the documentation
-- `deprecation`: Used if deprecating a feature or dropping support for a Python version.
+- `deprecations`: Used if deprecating a feature or dropping support for a Python version.
+- `data`: An update to the bundled time zone data.
 - `misc`: A change that has no interesting effect for end users, such as fixes to the test suite or CI.
 
 PRs that include a feature or bugfix *and* a deprecation should create a separate entry for the deprecation.
@@ -93,20 +94,45 @@ pip install -r requirements-dev.txt
 
 ## Testing
 
-The best way to test `dateutil` is to run `tox`. By default, `tox` will test against all supported versions of Python installed on your system. To limit the number of tests, run a specific subset of environments. For example, to run only on Python 2.7 and Python 3.6:
+The best way to test `dateutil` is to run `tox`. By default, `tox` will test against all supported versions of Python installed on your system. To limit the number of tests, run a specific subset of environments. For example, to run only on Python 3.11 and Python 3.13:
 
 ```bash
-tox -e py27,py36
+tox -e py311,py313
 ```
 
+For faster environment creation and dependency installation, you can install
+`tox` with the `tox-uv` plugin using [uv](https://docs.astral.sh/uv/):
+
+```bash
+uv tool install tox --with tox-uv
+```
+
+The same `tox` commands work with either the uv plugin or the default installer.
+
 You can also pass arguments to `pytest` through `tox` by placing them after `--`:
 
 ```bash
-tox -e py36 -- -m tzstr
+tox -e py311 -- -m tzstr
 ```
 
 This will pass the `-m tzstr` parameter to `pytest`, running only the tests with the `tzstr` mark.
 
+`tox` runs the tests in parallel with [pytest-xdist](https://pytest-xdist.readthedocs.io/). To run them in a single process, for example to use `--pdb`, pass `-n 0`:
+
+```bash
+tox -e py311 -- -n 0 --pdb
+```
+
 The tests can also be run directly by running `pytest` or `python -m pytest` in the root directory. This will be likely be less thorough but is often faster and is a good first pass to check your changes.
 
-All GitHub pull requests are automatically tested using [Travis](https://travis-ci.org/dateutil/dateutil/) and [Appveyor](https://ci.appveyor.com/project/dateutil/dateutil).
+The GitHub Actions workflows are checked with [zizmor](https://docs.zizmor.sh/).
+To run the audit locally:
+
+```bash
+uvx zizmor .github/workflows
+```
+
+This uses the latest zizmor release, which may report different findings from
+the version bundled with the pinned zizmor action in CI.
+
+All GitHub pull requests are automatically tested using [GitHub Actions](https://github.com/dateutil/dateutil/actions/).

{python-dateutil-2.9.0.post0 → python_dateutil-4.0.0}/NEWS

@@ -1,3 +1,165 @@
+Version 4.0.0 (2026-11-01)
+==========================
+
+``dateutil`` 4.0 requires Python 3.11 or later and no longer depends on
+``six``. Apart from that, the changes in this release are bug fixes, but note
+that ``isoparse`` is now stricter about the numeric fields it accepts (see
+below).
+
+
+Deprecations
+------------
+
+- Dropped support for Python versions older than 3.11 and removed the dependency
+  on ``six``, along with Python 2 compatibility helpers that were never part of
+  the public API, such as ``dateutil.tz.tzname_in_python2``. (gh pr #1625)
+
+
+Bugfixes
+--------
+
+- ``parser.isoparse``, and the ``isoparser`` methods ``parse_isodate``,
+  ``parse_isotime`` and ``parse_tzstr``, now require each numeric field to be
+  exactly the expected number of ASCII digits. Strings that were previously
+  accepted, such as ``20200728121240`` (read as 21:24), ``2014- 4-21`` and
+  ``2_14-04-21``, and offsets such as ``+-1:00``, now raise ``ValueError``.
+  ``tzical`` applies the same check to ``TZOFFSETFROM`` and ``TZOFFSETTO``.
+  Reported by @janos-gonye (gh issue #1074). Fixed by @varun3257 (gh pr #1617).
+- Fixed an issue where iterating over a cached ``rrule`` or ``rruleset`` could
+  hang forever if another iterator over the same rule had already completed the
+  cache, for example when a cached ``rrule`` was included twice in an
+  ``rruleset``. Reported by @bysiber (gh pr #1455). Fixed by @pganssle (gh pr
+  #1655).
+- Unpickling a ``tzutc`` now gives the ``dateutil.tz.UTC`` singleton, and
+  unpickling a ``tzoffset`` gives the same object as calling
+  ``tzoffset(name, offset)``. Previously unpickling bypassed the
+  singleton-generation logic. Reported and fixed by @masipcat (gh issue #1051,
+  gh pr #1053).
+- ``relativedelta(yearday=366)`` now resolves to December 31 in leap years.
+  Previously it gave December 30, the same date as ``yearday=365``. Reported
+  and fixed by @Master-Norna (gh pr #1583).
+
+
+Misc
+----
+
+- The build backend is now Hatchling, and the package metadata is in
+  ``pyproject.toml``. Versions are still derived from Git tags and exposed as
+  ``dateutil.__version__``. This mainly affects people building ``dateutil``
+  from source. (gh pr #1637, #1638)
+- Changes to CI, tests and release tooling that do not affect users of the
+  package: gh pr #1636, #1644, #1645, #1646, #1648, #1649, #1650.
+
+
+Version 3.0.0 (2026-10-21)
+==========================
+
+**This is the last major version of** ``dateutil`` **that will support any
+version of Python older than 3.11.** The next release will be the 4.x series,
+which will support Python 3.11 and later. We may release fixes for serious bugs
+in the 3.0.x series, but there are no plans for new features there.
+
+The biggest change in this release is a rewrite of ``tz.tzfile``, which affects
+nearly every user of ``dateutil.tz`` and changes the UTC offset of
+nonexistent times (see below). ``dateutil`` also now depends on the ``tzdata``
+package, and no longer ships its own time zone database.
+
+
+Data updates
+------------
+
+- ``dateutil`` no longer bundles a copy of the IANA time zone database. Time
+  zone data now comes from the system (see ``dateutil.tz.TZPATH``) or, failing
+  that, from the new ``tzdata`` dependency, so the data version is whatever
+  version of ``tzdata`` is installed. (gh pr #1130)
+
+
+Features
+--------
+
+- Rewrote ``tz.tzfile`` based on a backport of the ``zoneinfo`` module's pure-Python
+  implementation. This adds support for Version 2 and Version 3 ``tzfile(5)`` binaries,
+  resolving issues with timestamps beyond 2038 and "slim" format binaries. (gh issues #462, #1059, gh pr #1130)
+- Added ``dateutil.tz.TZPATH`` and ``dateutil.tz.reset_tzpath`` to allow for
+  runtime configuration of the IANA time zone data search path. These replace the
+  mutable ``dateutil.tz.TZPATHS`` list, which has been removed. (gh pr #1130)
+- ``dateutil`` now depends on the ``tzdata`` package, which ``gettz`` consults after the search
+  path and before the Windows registry. On Windows this means that names that are
+  both IANA keys and Windows time zone names, such as ``"UTC"``, now return a
+  ``tzfile`` rather than a ``tzwin``. (gh pr #1130)
+
+
+Bugfixes
+--------
+
+- ``tz.tzfile`` now follows PEP 495 for times that fall in a gap: with ``fold=0``
+  it uses the offset from before the transition, and with ``fold=1`` the offset
+  from after it. Previously it always used the offset from after the transition,
+  so for example ``datetime(2003, 4, 6, 2, 30, tzinfo=tz.gettz("America/New_York"))``
+  had a UTC offset of -04:00, where it now has -05:00, the same as with
+  ``zoneinfo``. (gh pr #1130)
+- ``tz.tzfile`` objects for fixed-offset zones, such as ``tz.gettz("UTC")``, now
+  return their offset, DST offset and abbreviation when ``utcoffset``, ``dst``
+  and ``tzname`` are called with ``None``, as ``tz.tzutc``, ``tz.tzoffset`` and
+  ``zoneinfo.ZoneInfo`` do. This means that ``datetime.time`` objects with such
+  a zone attached are now aware: ``time(12, tzinfo=tz.gettz("UTC")).isoformat()``
+  is now ``"12:00:00+00:00"`` rather than ``"12:00:00"``. (gh pr #1130)
+- ``tz.tzfile`` now infers ``dst()`` from the standard time on both sides of
+  each DST period, rather than only the one before it, and does so for each
+  transition rather than for each local time type. This fixes ``dst()`` for
+  double summer time (e.g. in ``Europe/London`` in the 1940s), for half-hour DST
+  (e.g. in ``Pacific/Rarotonga``) and where the standard offset changed at the
+  same time as a DST transition (e.g. in ``America/Bahia_Banderas`` in 2010).
+  Against the standard offsets in the tz database source, the only remaining
+  errors are in ``Europe/Paris`` in 1944 and 1945. (gh pr #1130)
+- Fixed ``rrulestr`` raising ``ValueError`` on experimental ``X-`` parameters in
+  an ``RRULE`` line (such as GNOME Evolution's ``X-EVOLUTION-ENDDATE``); these are
+  now ignored as RFC 5545 permits. Fixed by @yajo (gh pr #1374)
+- Enabled pickling and deepcopy of cached ``rrule`` and ``rruleset`` instances.
+  The cache setting is preserved, and cached results are regenerated on demand
+  without copying locks or generators. Reported by @niccokunzmann (gh issue #1369).
+  Fixed by @Jay1023CN (gh pr #1600).
+- Fixed ``relativedelta.__ne__`` raising ``TypeError`` when comparing against an
+  unsupported type such as ``None``; it now returns ``True``. Reported and fixed
+  by @kevinkt1 (gh issue #1157, gh pr #1158)
+- Raised the minimum version of ``six`` to 1.6, fixing ``No module named
+  'six.moves'`` errors with older versions. Reported by @skytreader (gh issue #1415),
+  fixed by @jdarias3 (gh pr #1424).
+
+
+Deprecations
+------------
+
+- Deprecated the ``dateutil.zoneinfo`` module. The module now acts as a wrapper
+  around the ``tzdata`` package and will be removed in a future version. Users are
+  encouraged to migrate to ``dateutil.tz.gettz`` or the standard library's
+  ``zoneinfo`` module. ``dateutil.zoneinfo.rebuild.rebuild`` no longer does
+  anything, and by default raises ``RebuildDeprecationWarning`` as an error;
+  filter the warning to call it as a no-op. (gh pr #1130)
+- Deprecated passing ``gettz`` a relative key that refers to a file outside of
+  every directory on ``TZPATH``, such as ``"../../etc/localtime"``. By default
+  this now raises ``dateutil.tz.DeprecatedTzKeyWarning`` as an error; filter the
+  warning to keep the old behavior for now, or pass an absolute path instead.
+  (gh pr #1130)
+
+
+Documentation changes
+---------------------
+
+- Added intersphinx to the docs build and cleaned up some broken links. (gh pr #1463)
+
+
+Misc
+----
+
+- Releases are now uploaded to PyPI using trusted publishing, and the built
+  sdist and wheel are tested on all supported platforms before upload.
+  (gh pr #1619, #1622)
+- Changes to CI, tests and release tooling that do not affect users of the
+  package: gh pr #1417, #1462, #1464, #1465, #1466, #1467, #1468, #1469, #1470,
+  #1499, #1501, #1504, #1576, #1577, #1578, #1581, #1585.
+
+
 Version 2.9.0.post0 (2024-03-01)
 ================================
 

{python-dateutil-2.9.0.post0/src/python_dateutil.egg-info → python_dateutil-4.0.0}/PKG-INFO

@@ -1,38 +1,31 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.5
 Name: python-dateutil
-Version: 2.9.0.post0
+Version: 4.0.0
 Summary: Extensions to the standard Python datetime module
-Home-page: https://github.com/dateutil/dateutil
-Author: Gustavo Niemeyer
-Author-email: gustavo@niemeyer.net
-Maintainer: Paul Ganssle
-Maintainer-email: dateutil@python.org
-License: Dual License
+Project-URL: Homepage, https://github.com/dateutil/dateutil
 Project-URL: Documentation, https://dateutil.readthedocs.io/en/stable/
 Project-URL: Source, https://github.com/dateutil/dateutil
+Author-email: Gustavo Niemeyer <gustavo@niemeyer.net>
+Maintainer-email: Paul Ganssle <dateutil@python.org>
+License-Expression: BSD-3-Clause
+License-File: AUTHORS.md
+License-File: LICENSE
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: BSD License
-Classifier: License :: OSI Approved :: Apache Software License
 Classifier: Programming Language :: Python
-Classifier: Programming Language :: Python :: 2
-Classifier: Programming Language :: Python :: 2.7
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.3
-Classifier: Programming Language :: Python :: 3.4
-Classifier: Programming Language :: Python :: 3.5
-Classifier: Programming Language :: Python :: 3.6
-Classifier: Programming Language :: Python :: 3.7
-Classifier: Programming Language :: Python :: 3.8
-Classifier: Programming Language :: Python :: 3.9
-Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Programming Language :: Python :: Free Threading :: 2 - Beta
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
 Classifier: Topic :: Software Development :: Libraries
-Requires-Python: !=3.0.*,!=3.1.*,!=3.2.*,>=2.7
+Requires-Python: >=3.11
+Requires-Dist: tzdata
 Description-Content-Type: text/x-rst
-License-File: LICENSE
-Requires-Dist: six>=1.5
 
 dateutil - powerful extensions to datetime
 ==========================================
@@ -41,7 +34,7 @@ dateutil - powerful extensions to datetime
 
 |gitter| |readthedocs|
 
-|travis| |appveyor| |pipelines| |coverage|
+|gha| |coverage|
 
 .. |pypi| image:: https://img.shields.io/pypi/v/python-dateutil.svg?style=flat-square
     :target: https://pypi.org/project/python-dateutil/
@@ -51,17 +44,9 @@ dateutil - powerful extensions to datetime
     :target: https://pypi.org/project/python-dateutil/
     :alt: supported Python version
 
-.. |travis| image:: https://img.shields.io/travis/dateutil/dateutil/master.svg?style=flat-square&label=Travis%20Build
-    :target: https://travis-ci.org/dateutil/dateutil
-    :alt: travis build status
-
-.. |appveyor| image:: https://img.shields.io/appveyor/ci/dateutil/dateutil/master.svg?style=flat-square&logo=appveyor
-    :target: https://ci.appveyor.com/project/dateutil/dateutil
-    :alt: appveyor build status
-
-.. |pipelines| image:: https://dev.azure.com/pythondateutilazure/dateutil/_apis/build/status/dateutil.dateutil?branchName=master
-    :target: https://dev.azure.com/pythondateutilazure/dateutil/_build/latest?definitionId=1&branchName=master
-    :alt: azure pipelines build status
+.. |gha| image:: https://github.com/dateutil/dateutil/actions/workflows/validate.yml/badge.svg
+    :target: https://github.com/dateutil/dateutil/actions
+    :alt: github actions build status
 
 .. |coverage| image:: https://codecov.io/gh/dateutil/dateutil/branch/master/graphs/badge.svg?branch=master
     :target: https://codecov.io/gh/dateutil/dateutil?branch=master
@@ -189,11 +174,6 @@ Releases     Signing key fingerprint
 New releases *may* have signed tags, but binary and source distributions
 uploaded to PyPI will no longer have GPG signatures attached.
 
-Contact
-=======
-Our mailing list is available at `dateutil@python.org <https://mail.python.org/mailman/listinfo/dateutil>`_. As it is hosted by the PSF, it is subject to the `PSF code of
-conduct <https://www.python.org/psf/conduct/>`_.
-
 License
 =======
 

{python-dateutil-2.9.0.post0 → python_dateutil-4.0.0}/README.rst

@@ -5,7 +5,7 @@ dateutil - powerful extensions to datetime
 
 |gitter| |readthedocs|
 
-|travis| |appveyor| |pipelines| |coverage|
+|gha| |coverage|
 
 .. |pypi| image:: https://img.shields.io/pypi/v/python-dateutil.svg?style=flat-square
     :target: https://pypi.org/project/python-dateutil/
@@ -15,17 +15,9 @@ dateutil - powerful extensions to datetime
     :target: https://pypi.org/project/python-dateutil/
     :alt: supported Python version
 
-.. |travis| image:: https://img.shields.io/travis/dateutil/dateutil/master.svg?style=flat-square&label=Travis%20Build
-    :target: https://travis-ci.org/dateutil/dateutil
-    :alt: travis build status
-
-.. |appveyor| image:: https://img.shields.io/appveyor/ci/dateutil/dateutil/master.svg?style=flat-square&logo=appveyor
-    :target: https://ci.appveyor.com/project/dateutil/dateutil
-    :alt: appveyor build status
-
-.. |pipelines| image:: https://dev.azure.com/pythondateutilazure/dateutil/_apis/build/status/dateutil.dateutil?branchName=master
-    :target: https://dev.azure.com/pythondateutilazure/dateutil/_build/latest?definitionId=1&branchName=master
-    :alt: azure pipelines build status
+.. |gha| image:: https://github.com/dateutil/dateutil/actions/workflows/validate.yml/badge.svg
+    :target: https://github.com/dateutil/dateutil/actions
+    :alt: github actions build status
 
 .. |coverage| image:: https://codecov.io/gh/dateutil/dateutil/branch/master/graphs/badge.svg?branch=master
     :target: https://codecov.io/gh/dateutil/dateutil?branch=master
@@ -153,11 +145,6 @@ Releases     Signing key fingerprint
 New releases *may* have signed tags, but binary and source distributions
 uploaded to PyPI will no longer have GPG signatures attached.
 
-Contact
-=======
-Our mailing list is available at `dateutil@python.org <https://mail.python.org/mailman/listinfo/dateutil>`_. As it is hosted by the PSF, it is subject to the `PSF code of
-conduct <https://www.python.org/psf/conduct/>`_.
-
 License
 =======
 

python_dateutil-4.0.0/ci_tools/run_tz_master_env.sh

@@ -0,0 +1,97 @@
+#!/usr/bin/env bash
+
+###
+# Runs the 'tz' tox test environment, which builds the repo against the master
+# branch of the upstream tz database project.
+
+set -e
+
+TMP_DIR=$(readlink -f ${1})
+REPO_DIR=$(readlink -f ${2})
+ORIG_DIR=$(pwd)
+
+UPSTREAM_URL="https://github.com/eggert/tz.git"
+
+if [ -n "$TF_BUILD" ]; then
+    EXTRA_TEST_ARGS=--junitxml=../unittests/TEST-tz.xml
+fi
+
+# Work in a temporary directory
+cd $TMP_DIR
+
+# Clone or update the repo
+DIR_EXISTS=false
+if [ -d tz ]; then
+    cd tz
+    if [[ $(git remote get-url origin) == ${UPSTREAM_URL} ]]; then
+        git fetch origin main
+        git reset --hard origin/main
+        DIR_EXISTS=true
+    else
+        cd ..
+        rm -rf tz
+    fi
+fi
+
+if [ "$DIR_EXISTS" = false ]; then
+    git clone ${UPSTREAM_URL}
+    cd tz
+fi
+
+# Build and install the compiled zoneinfo files, as "fat" TZif files of the
+# "main" data form unless TZ_BLOAT and TZ_DATAFORM say otherwise
+TZ_BLOAT=${TZ_BLOAT:-fat}
+TZ_DATAFORM=${TZ_DATAFORM:-main}
+make ZFLAGS="-b ${TZ_BLOAT}" DATAFORM="${TZ_DATAFORM}" \
+    TOPDIR="${TMP_DIR}/tzdir" install
+
+cd $ORIG_DIR
+
+# Make sure that the tests will actually see the data we just built. The
+# tests that are about the data on TZPATH block the tzdata package
+# themselves (see the tz_source fixture), so that anything missing from or
+# unreadable in this data fails, rather than being answered by tzdata.
+TZ_BLOAT=${TZ_BLOAT} TZ_DATAFORM=${TZ_DATAFORM} python - <<'EOF'
+import os
+import struct
+import sys
+
+from dateutil import tz
+
+tzpath = os.environ["PYTHONTZPATH"]
+
+if tuple(tz.TZPATH) != (tzpath,):
+    sys.exit("Expected TZPATH to be (%r,), got %r" % (tzpath, tz.TZPATH))
+
+# tzdata.zi starts with a "# version" line, followed by a "# dataform" line
+# for anything other than the main data form.
+with open(os.path.join(tzpath, "tzdata.zi")) as f:
+    header = [f.readline().strip() for _ in range(2)]
+print("Testing against: %s" % header[0])
+
+dataform = "main"
+if header[1].startswith("# dataform "):
+    dataform = header[1].split()[-1]
+if dataform != os.environ["TZ_DATAFORM"]:
+    sys.exit(
+        "Expected the %s data form, got %s" % (os.environ["TZ_DATAFORM"], dataform)
+    )
+print("Using the %s data form" % dataform)
+
+zone = tz.gettz("America/New_York")
+if zone is None or not zone._filename.startswith(tzpath):
+    sys.exit("America/New_York was not loaded from %s: %r" % (tzpath, zone))
+
+# Slim files have an empty version 1 data block, fat files do not.
+with open(zone._filename, "rb") as f:
+    v1_timecnt = struct.unpack(">6l", f.read(44)[20:])[3]
+
+bloat = "fat" if v1_timecnt else "slim"
+if bloat != os.environ["TZ_BLOAT"]:
+    sys.exit("Expected %s TZif files, got %s" % (os.environ["TZ_BLOAT"], bloat))
+print("Using %s TZif files" % bloat)
+EOF
+
+# Run the tests
+python -m pytest ${REPO_DIR}/tests $EXTRA_TEST_ARGS -x
+