zpdatafetch 2.1.1__tar.gz → 2.2.0__tar.gz

{zpdatafetch-2.1.1/src/zpdatafetch.egg-info → zpdatafetch-2.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: zpdatafetch
-Version: 2.1.1
+Version: 2.2.0
 Summary: A package for fetching data from Zwiftpower and Zwiftracing.app
 Author-email: Doug Morris <doug@mhost.com>
 License-Expression: MIT
@@ -24,9 +24,9 @@ Provides-Extra: trio
 Requires-Dist: trio>=0.26.0; extra == "trio"
 Dynamic: license-file
 
-# zpdatafetch & zrdatafetch
+# zpdatafetch, zrdatafetch & zsdatafetch
 
-A python library and command-line tool for fetching data from ZwiftPower.com and Zwiftracing.app APIs.
+A python library and command-line tool for fetching data from ZwiftPower.com, Zwiftracing.app, and Zwift Status APIs.
 
 ## Installation
 
@@ -50,16 +50,19 @@ real free-threaded environment. Please do
 
 ## Overview
 
-This package provides two main command-line tools:
+This package provides four command-line tools:
 
-| Tool         | API         | Purpose                              | Data Types                                                |
-| ------------ | ----------- | ------------------------------------ | --------------------------------------------------------- |
-| **`zpdata`** | ZwiftPower  | Race rankings, signups, results      | Cyclist, Primes, Results, Signups, Sprints, Teams, League |
-| **`zrdata`** | Zwiftracing | Rider ratings, race results, rosters | Rider Ratings, Race Results, Team Rosters                 |
+| Tool         | API          | Purpose                                    | Data Types                                                |
+| ------------ | ------------ | ------------------------------------------ | --------------------------------------------------------- |
+| **`zpdata`** | ZwiftPower   | Race rankings, signups, results            | Cyclist, Primes, Results, Signups, Sprints, Teams, League |
+| **`zrdata`** | Zwiftracing  | Rider ratings, race results, rosters       | Rider Ratings, Race Results, Team Rosters                 |
+| **`zdata`**  | Zwift        | Profiles, followers, activities, worlds    | Profile, Followers, RideOns, Activity, Worlds, Riders     |
+| **`zsdata`** | Zwift Status | Service status, incidents, maintenance     | Summary, Components, Incidents, Maintenance               |
 
-Both tools support batch operations, flexible logging, and can be used as
-standalone CLI tools or imported as libraries. They maintain separate credential
-stores for each API.
+All tools support flexible logging and can be used as standalone CLI tools or
+imported as Python libraries. `zpdata`, `zrdata`, and `zdata` require
+credentials; `zsdata` uses the public Zwift Status API (no authentication
+required).
 
 ## Key Features
 
@@ -80,6 +83,22 @@ stores for each API.
 - **Race results** - Complete race result data with rating changes
 - **Team rosters** - Full team member details and power metrics
 
+### For zdata (Zwift)
+
+- **Rider profiles** - Fetch rider profile data by Zwift ID
+- **Followers** - Follower and followee lists with filtering
+- **RideOns** - Fetch RideOn data or give RideOns to activities
+- **Activity history** - Fetch activity data with pagination
+- **Worlds** - List currently active Zwift worlds
+- **Riders in world** - See who is riding in a specific world
+
+### For zsdata (Zwift Status)
+
+- **Service status** - Overall system status and component health
+- **Components** - Individual service component status (Game, Web, Companion, etc.)
+- **Incidents** - Current and historical incident reports with timelines
+- **Maintenance** - Scheduled maintenance windows (all, upcoming, active)
+
 ### Common Features
 
 - **Async support** - Concurrent fetching with asyncio or trio backends
@@ -107,10 +126,16 @@ For Zwiftracing (`zrdata`), you will need your Zwiftracing API authorization hea
 
 ```sh
 keyring set zrdatafetch authorization
-# or wioth zrdata
+# or with zrdata
 zrdata config
 ```
 
+For Zwift (`zdata`), you will need your Zwift account credentials:
+
+```sh
+zdata config
+```
+
 In principle, the library can use alternate backend keyrings, but I have not
 tested this so far. At the moment, only the system keyring is used. See [the
 keyring docs](https://keyring.readthedocs.io/en/latest/) for more details on how
@@ -295,7 +320,7 @@ including rider ratings, race results, and team rosters.
 
 ```sh
 usage: zrdata [-h] [-v] [-vv] [--log-file PATH] [-r] [--v1fetch] [--noaction] [--sync]
-              [--batch] [--batch-file FILE] [--premium]
+              [--batch] [--batch-file FILE] [--premium] [--at DATETIME]
               [{config,rider,result,team}] [id ...]
 
 Module for fetching Zwiftracing data using the Zwiftracing API
@@ -317,6 +342,7 @@ options:
   --batch               use batch POST endpoint for multiple IDs (rider command only)
   --batch-file FILE     read IDs from file (one per line) for batch request (rider command only)
   --premium             use premium tier rate limits (higher request quotas)
+  --at DATETIME         fetch historical ratings at a date/time in UTC (rider command only)
 ```
 
 **Note:** All objects support both synchronous (`fetch()`) and asynchronous (`afetch()`) methods. See the Async API section below for details.
@@ -349,6 +375,28 @@ zrdata config
 zrdata config  # Will prompt for authorization header
 ```
 
+### Historical Ratings
+
+Use `--at` to fetch rider ratings at a specific point in time. Accepts ISO 8601
+date/time strings, interpreted as UTC:
+
+```sh
+# Fetch ratings as of a specific date
+zrdata rider --at 2024-06-15 12345
+
+# Fetch ratings at a specific date and time
+zrdata rider --at "2024-06-15 14:30" 12345
+
+# ISO 8601 with T separator
+zrdata rider --at 2024-06-15T14:30:00 12345
+
+# Combine with batch
+zrdata rider --batch --at 2024-06-15 12345 67890 11111
+
+# Preview what would be fetched
+zrdata rider --noaction --at 2024-06-15 12345
+```
+
 ### Advanced Options
 
 ```sh
@@ -735,10 +783,11 @@ async def main():
         for zwift_id, rider in riders.items():
             print(f"{rider.name}: {rider.current_rating}")
 
-        # Batch fetch with historical data
+        # Batch fetch with historical data (epoch is a Unix timestamp)
+        from shared.validation import parse_datetime_to_epoch
         historical = await ZRRider.afetch_batch(
             12345, 67890,
-            epoch=1704067200,  # Unix timestamp
+            epoch=parse_datetime_to_epoch('2024-01-01'),
             zr=zr
         )
 
@@ -1130,6 +1179,108 @@ obj.asdict() # return the data as a dictionary
 print(obj) # effectively the same as obj.asdict()
 ```
 
+## Zwift Data (zdata)
+
+The `zdata` command-line tool provides access to Zwift's unofficial API for
+rider profiles, social data, activities, and world information. Requires Zwift
+account credentials.
+
+### Command-line usage
+
+```sh
+zdata config                        # Set up Zwift credentials
+zdata profile 550564                # Fetch rider profile
+zdata profile 550564 123456         # Fetch multiple profiles
+zdata followers 550564              # Fetch followers and followees
+zdata followers --followers-only 550564  # Followers only
+zdata followers --followees-only 550564  # Followees only
+zdata rideons 550564 12345678       # Fetch RideOns (rider_id activity_id)
+zdata rideons --give 550564 12345678  # Give a RideOn
+zdata activity 550564               # Fetch activity history
+zdata activity --limit 50 550564    # Fetch 50 activities
+zdata worlds                        # List active worlds
+zdata ridersinworld 1               # Riders in world by ID
+zdata ridersinworld watopia         # Riders in world by name
+zdata profile --raw 550564          # Raw JSON output
+zdata -v profile 550564             # Verbose logging
+```
+
+### Library usage
+
+```python
+from zdatafetch import (
+    ZwiftProfile,
+    ZwiftFollowers,
+    ZwiftRideOns,
+    ZwiftActivity,
+    ZwiftWorlds,
+    ZwiftRidersInWorld,
+)
+
+# Fetch rider profile
+profile = ZwiftProfile()
+profile.fetch(550564)
+print(profile.json())
+
+# Fetch followers
+followers = ZwiftFollowers()
+followers.fetch(550564)
+print(f"Followers: {followers.follower_count()}")
+
+# Fetch activity history
+activity = ZwiftActivity()
+activity.fetch(550564, start=0, limit=20)
+
+# List active worlds
+worlds = ZwiftWorlds()
+worlds.fetch()
+
+# Give a RideOn
+ZwiftRideOns.give_rideon(550564, 12345678)
+```
+
+## Zwift Status Data (zsdata)
+
+The `zsdata` command-line tool provides access to the public Zwift Status API
+(powered by Statuspage.io). No authentication required.
+
+### Command-line usage
+
+```sh
+zsdata status                       # Overall status summary
+zsdata status --components          # Component list only
+zsdata incidents                    # All incidents
+zsdata incidents --unresolved       # Unresolved incidents only
+zsdata maintenance                  # All scheduled maintenance
+zsdata maintenance --upcoming       # Upcoming maintenance only
+zsdata maintenance --active         # Active maintenance only
+zsdata status --raw                 # Raw JSON output
+zsdata status --json                # Parsed JSON output
+zsdata -v status                    # Verbose logging
+```
+
+### Library usage
+
+```python
+from zsdatafetch import ZSSummaryFetch, ZSIncidentFetch, ZSMaintenanceFetch
+
+# Get overall status
+summary = ZSSummaryFetch().fetch()
+print(summary.status.description)  # "All Systems Operational"
+for comp in summary.components:
+    print(f"  {comp.name}: {comp.status}")
+
+# Get unresolved incidents
+incidents = ZSIncidentFetch().fetch(unresolved_only=True)
+for incident in incidents:
+    print(f"{incident.name} ({incident.impact})")
+
+# Get upcoming maintenance
+maintenance = ZSMaintenanceFetch().fetch(upcoming=True)
+for m in maintenance:
+    print(f"{m.name}: {m.scheduled_for} - {m.scheduled_until}")
+```
+
 ## Development
 
 I've switched over to using [https://astral.sh/](Astral)'s

{zpdatafetch-2.1.1 → zpdatafetch-2.2.0}/README.md

@@ -1,6 +1,6 @@
-# zpdatafetch & zrdatafetch
+# zpdatafetch, zrdatafetch & zsdatafetch
 
-A python library and command-line tool for fetching data from ZwiftPower.com and Zwiftracing.app APIs.
+A python library and command-line tool for fetching data from ZwiftPower.com, Zwiftracing.app, and Zwift Status APIs.
 
 ## Installation
 
@@ -24,16 +24,19 @@ real free-threaded environment. Please do
 
 ## Overview
 
-This package provides two main command-line tools:
+This package provides four command-line tools:
 
-| Tool         | API         | Purpose                              | Data Types                                                |
-| ------------ | ----------- | ------------------------------------ | --------------------------------------------------------- |
-| **`zpdata`** | ZwiftPower  | Race rankings, signups, results      | Cyclist, Primes, Results, Signups, Sprints, Teams, League |
-| **`zrdata`** | Zwiftracing | Rider ratings, race results, rosters | Rider Ratings, Race Results, Team Rosters                 |
+| Tool         | API          | Purpose                                    | Data Types                                                |
+| ------------ | ------------ | ------------------------------------------ | --------------------------------------------------------- |
+| **`zpdata`** | ZwiftPower   | Race rankings, signups, results            | Cyclist, Primes, Results, Signups, Sprints, Teams, League |
+| **`zrdata`** | Zwiftracing  | Rider ratings, race results, rosters       | Rider Ratings, Race Results, Team Rosters                 |
+| **`zdata`**  | Zwift        | Profiles, followers, activities, worlds    | Profile, Followers, RideOns, Activity, Worlds, Riders     |
+| **`zsdata`** | Zwift Status | Service status, incidents, maintenance     | Summary, Components, Incidents, Maintenance               |
 
-Both tools support batch operations, flexible logging, and can be used as
-standalone CLI tools or imported as libraries. They maintain separate credential
-stores for each API.
+All tools support flexible logging and can be used as standalone CLI tools or
+imported as Python libraries. `zpdata`, `zrdata`, and `zdata` require
+credentials; `zsdata` uses the public Zwift Status API (no authentication
+required).
 
 ## Key Features
 
@@ -54,6 +57,22 @@ stores for each API.
 - **Race results** - Complete race result data with rating changes
 - **Team rosters** - Full team member details and power metrics
 
+### For zdata (Zwift)
+
+- **Rider profiles** - Fetch rider profile data by Zwift ID
+- **Followers** - Follower and followee lists with filtering
+- **RideOns** - Fetch RideOn data or give RideOns to activities
+- **Activity history** - Fetch activity data with pagination
+- **Worlds** - List currently active Zwift worlds
+- **Riders in world** - See who is riding in a specific world
+
+### For zsdata (Zwift Status)
+
+- **Service status** - Overall system status and component health
+- **Components** - Individual service component status (Game, Web, Companion, etc.)
+- **Incidents** - Current and historical incident reports with timelines
+- **Maintenance** - Scheduled maintenance windows (all, upcoming, active)
+
 ### Common Features
 
 - **Async support** - Concurrent fetching with asyncio or trio backends
@@ -81,10 +100,16 @@ For Zwiftracing (`zrdata`), you will need your Zwiftracing API authorization hea
 
 ```sh
 keyring set zrdatafetch authorization
-# or wioth zrdata
+# or with zrdata
 zrdata config
 ```
 
+For Zwift (`zdata`), you will need your Zwift account credentials:
+
+```sh
+zdata config
+```
+
 In principle, the library can use alternate backend keyrings, but I have not
 tested this so far. At the moment, only the system keyring is used. See [the
 keyring docs](https://keyring.readthedocs.io/en/latest/) for more details on how
@@ -269,7 +294,7 @@ including rider ratings, race results, and team rosters.
 
 ```sh
 usage: zrdata [-h] [-v] [-vv] [--log-file PATH] [-r] [--v1fetch] [--noaction] [--sync]
-              [--batch] [--batch-file FILE] [--premium]
+              [--batch] [--batch-file FILE] [--premium] [--at DATETIME]
               [{config,rider,result,team}] [id ...]
 
 Module for fetching Zwiftracing data using the Zwiftracing API
@@ -291,6 +316,7 @@ options:
   --batch               use batch POST endpoint for multiple IDs (rider command only)
   --batch-file FILE     read IDs from file (one per line) for batch request (rider command only)
   --premium             use premium tier rate limits (higher request quotas)
+  --at DATETIME         fetch historical ratings at a date/time in UTC (rider command only)
 ```
 
 **Note:** All objects support both synchronous (`fetch()`) and asynchronous (`afetch()`) methods. See the Async API section below for details.
@@ -323,6 +349,28 @@ zrdata config
 zrdata config  # Will prompt for authorization header
 ```
 
+### Historical Ratings
+
+Use `--at` to fetch rider ratings at a specific point in time. Accepts ISO 8601
+date/time strings, interpreted as UTC:
+
+```sh
+# Fetch ratings as of a specific date
+zrdata rider --at 2024-06-15 12345
+
+# Fetch ratings at a specific date and time
+zrdata rider --at "2024-06-15 14:30" 12345
+
+# ISO 8601 with T separator
+zrdata rider --at 2024-06-15T14:30:00 12345
+
+# Combine with batch
+zrdata rider --batch --at 2024-06-15 12345 67890 11111
+
+# Preview what would be fetched
+zrdata rider --noaction --at 2024-06-15 12345
+```
+
 ### Advanced Options
 
 ```sh
@@ -709,10 +757,11 @@ async def main():
         for zwift_id, rider in riders.items():
             print(f"{rider.name}: {rider.current_rating}")
 
-        # Batch fetch with historical data
+        # Batch fetch with historical data (epoch is a Unix timestamp)
+        from shared.validation import parse_datetime_to_epoch
         historical = await ZRRider.afetch_batch(
             12345, 67890,
-            epoch=1704067200,  # Unix timestamp
+            epoch=parse_datetime_to_epoch('2024-01-01'),
             zr=zr
         )
 
@@ -1104,6 +1153,108 @@ obj.asdict() # return the data as a dictionary
 print(obj) # effectively the same as obj.asdict()
 ```
 
+## Zwift Data (zdata)
+
+The `zdata` command-line tool provides access to Zwift's unofficial API for
+rider profiles, social data, activities, and world information. Requires Zwift
+account credentials.
+
+### Command-line usage
+
+```sh
+zdata config                        # Set up Zwift credentials
+zdata profile 550564                # Fetch rider profile
+zdata profile 550564 123456         # Fetch multiple profiles
+zdata followers 550564              # Fetch followers and followees
+zdata followers --followers-only 550564  # Followers only
+zdata followers --followees-only 550564  # Followees only
+zdata rideons 550564 12345678       # Fetch RideOns (rider_id activity_id)
+zdata rideons --give 550564 12345678  # Give a RideOn
+zdata activity 550564               # Fetch activity history
+zdata activity --limit 50 550564    # Fetch 50 activities
+zdata worlds                        # List active worlds
+zdata ridersinworld 1               # Riders in world by ID
+zdata ridersinworld watopia         # Riders in world by name
+zdata profile --raw 550564          # Raw JSON output
+zdata -v profile 550564             # Verbose logging
+```
+
+### Library usage
+
+```python
+from zdatafetch import (
+    ZwiftProfile,
+    ZwiftFollowers,
+    ZwiftRideOns,
+    ZwiftActivity,
+    ZwiftWorlds,
+    ZwiftRidersInWorld,
+)
+
+# Fetch rider profile
+profile = ZwiftProfile()
+profile.fetch(550564)
+print(profile.json())
+
+# Fetch followers
+followers = ZwiftFollowers()
+followers.fetch(550564)
+print(f"Followers: {followers.follower_count()}")
+
+# Fetch activity history
+activity = ZwiftActivity()
+activity.fetch(550564, start=0, limit=20)
+
+# List active worlds
+worlds = ZwiftWorlds()
+worlds.fetch()
+
+# Give a RideOn
+ZwiftRideOns.give_rideon(550564, 12345678)
+```
+
+## Zwift Status Data (zsdata)
+
+The `zsdata` command-line tool provides access to the public Zwift Status API
+(powered by Statuspage.io). No authentication required.
+
+### Command-line usage
+
+```sh
+zsdata status                       # Overall status summary
+zsdata status --components          # Component list only
+zsdata incidents                    # All incidents
+zsdata incidents --unresolved       # Unresolved incidents only
+zsdata maintenance                  # All scheduled maintenance
+zsdata maintenance --upcoming       # Upcoming maintenance only
+zsdata maintenance --active         # Active maintenance only
+zsdata status --raw                 # Raw JSON output
+zsdata status --json                # Parsed JSON output
+zsdata -v status                    # Verbose logging
+```
+
+### Library usage
+
+```python
+from zsdatafetch import ZSSummaryFetch, ZSIncidentFetch, ZSMaintenanceFetch
+
+# Get overall status
+summary = ZSSummaryFetch().fetch()
+print(summary.status.description)  # "All Systems Operational"
+for comp in summary.components:
+    print(f"  {comp.name}: {comp.status}")
+
+# Get unresolved incidents
+incidents = ZSIncidentFetch().fetch(unresolved_only=True)
+for incident in incidents:
+    print(f"{incident.name} ({incident.impact})")
+
+# Get upcoming maintenance
+maintenance = ZSMaintenanceFetch().fetch(upcoming=True)
+for m in maintenance:
+    print(f"{m.name}: {m.scheduled_for} - {m.scheduled_until}")
+```
+
 ## Development
 
 I've switched over to using [https://astral.sh/](Astral)'s

{zpdatafetch-2.1.1 → zpdatafetch-2.2.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "zpdatafetch"
-version = "2.1.1"
+version = "2.2.0"
 description = "A package for fetching data from Zwiftpower and Zwiftracing.app"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -39,6 +39,7 @@ Repository = "https://github.com/puckdoug/zpdatafetch"
 zdata = "zdatafetch.cli:main"
 zpdata = "zpdatafetch.cli:main"
 zrdata = "zrdatafetch.cli:main"
+zsdata = "zsdatafetch.cli:main"
 
 [project.optional-dependencies]
 # For users who want both backends
@@ -124,10 +125,6 @@ select = [
   "UP",  # pyupgrade
   "ANN",  # flake8-annotations (type hints)
 ]
-ignore = [
-  "ANN101",  # Missing type annotation for self
-  "ANN102",  # Missing type annotation for cls
-]
 
 # Per-file ignores for justified Any usage
 [tool.ruff.lint.per-file-ignores]
@@ -148,6 +145,8 @@ ignore = [
 "src/zpdatafetch/*.py" = ["E501"]
 # zdatafetch files have decorative comment lines that exceed 80 chars
 "src/zdatafetch/*.py" = ["E501"]
+# zsdatafetch async_zs uses Any for context manager exc params
+"src/zsdatafetch/async_zs.py" = ["ANN401"]
 # Test files don't need type annotations (fixtures don't have types) and allow long lines
 "test/**/*.py" = ["ANN001", "ANN002", "ANN003", "ANN201", "ANN202", "E501"]
 

{zpdatafetch-2.1.1 → zpdatafetch-2.2.0}/src/shared/cli.py

@@ -5,6 +5,7 @@ functionality for both zpdatafetch and zrdatafetch CLIs.
 """
 
 import logging
+import sys
 from argparse import ArgumentParser, Namespace
 from collections.abc import Callable
 from importlib.metadata import PackageNotFoundError, version
@@ -82,21 +83,6 @@ def create_base_parser(
     action='store_true',
     help='output fetched data as JSON (default: object repr)',
   )
-  parser.add_argument(
-    '--extras',
-    action='store_true',
-    help='report recently added fields not handled natively',
-  )
-  parser.add_argument(
-    '--excluded',
-    action='store_true',
-    help='report recognized fields not yet explicitly handled',
-  )
-  parser.add_argument(
-    '--v1fetch',
-    action='store_true',
-    help='output fetched data in v1.8 format (for backward compatibility)',
-  )
 
   # Dry-run argument
   parser.add_argument(
@@ -216,7 +202,7 @@ def validate_command_name(
     True if valid, False if invalid.
   """
   if cmd not in valid_commands:
-    print(f'Error: Unknown command "{cmd}"')
+    print(f'Error: Unknown command "{cmd}"', file=sys.stderr)
     return False
   return True
 
@@ -235,7 +221,7 @@ def validate_ids_provided(
     True if IDs provided, False otherwise.
   """
   if not ids:
-    print(f'Error: {cmd} command requires one or more IDs')
+    print(f'Error: {cmd} command requires one or more IDs', file=sys.stderr)
     return False
   return True
 
@@ -271,5 +257,5 @@ def read_ids_from_file(filepath: str) -> list[str] | None:
     with open(filepath) as f:
       return [line.strip() for line in f if line.strip()]
   except OSError as e:
-    print(f'Error reading batch file: {e}')
+    print(f'Error reading batch file: {e}', file=sys.stderr)
     return None

{zpdatafetch-2.1.1 → zpdatafetch-2.2.0}/src/shared/validation.py

@@ -15,7 +15,9 @@ These ranges are based on Python's native integer limits and observed
 API behavior.
 """
 
+import calendar
 import sys
+from datetime import datetime, timezone
 from typing import Literal
 
 # ID Range Constants
@@ -178,6 +180,44 @@ def validate_epoch(value: int) -> int:
   return value
 
 
+def parse_datetime_to_epoch(value: str) -> int:
+  """Parse a date/time string to a validated Unix epoch timestamp (UTC).
+
+  Accepts ISO 8601 formats:
+    - '2024-06-15'              (date only, midnight UTC)
+    - '2024-06-15 14:30'        (date and time, UTC)
+    - '2024-06-15T14:30:00'     (ISO 8601, UTC)
+    - '2024-06-15T14:30:00Z'    (ISO 8601 with Z suffix)
+    - '2024-06-15T14:30:00+00:00' (ISO 8601 with timezone)
+
+  Args:
+      value: Date/time string to parse
+
+  Returns:
+      Unix epoch timestamp (int, UTC)
+
+  Raises:
+      ValidationError: If the string cannot be parsed or the resulting
+          epoch is out of range
+  """
+  try:
+    # Replace trailing 'Z' with '+00:00' for Python 3.10 compatibility
+    normalized = value.replace('Z', '+00:00') if value.endswith('Z') else value
+    dt = datetime.fromisoformat(normalized)
+  except ValueError as e:
+    raise ValidationError(
+      f"Invalid date/time '{value}': use ISO 8601 format "
+      f"(e.g. '2024-06-15' or '2024-06-15T14:30:00')",
+    ) from e
+
+  # Assume UTC if no timezone specified
+  if dt.tzinfo is None:
+    dt = dt.replace(tzinfo=timezone.utc)
+
+  epoch = calendar.timegm(dt.utctimetuple())
+  return validate_epoch(epoch)
+
+
 def validate_batch_size(count: int, max_size: int = MAX_BATCH_SIZE) -> None:
   """Validate batch request size.