How kevinw14/nascarpylon works
NascarPylon is a terminal NASCAR live-race monitor. The user selects a series in the program; the client loads NASCAR’s operations feed to find that series’ live-feed URL, fetches and parses race data, and the terminal refreshes the standings every two seconds with lap, flag, and position-change indicators. The feed models also parse vehicle pit stops, while the operations feed exposes driver-points URLs that this workflow does not fetch. Relationships reflect the shown calls and object construction; no separate storage layer is present.
Main entry points: main.py Race monitor · ApiClient.py API client · LiveFeed.py Live race feed · Vehicle.py Vehicle data
Components 11
Terminal display
- Race monitor
src/main.py - Terminal colors
src/Colors.py
Feed access
- API client
src/ApiClient.py
Feed models
- Flag states
src/FlagStatus.py - Race series
src/Series.py - Operations feed
src/OpsFeed.py - Live race feed
src/LiveFeed.py - Vehicle data
src/Vehicle.py - Pit stop data
src/PitStop.py
Other components
- Operator
- NASCAR feed service
Connections 12
- Operator → Race monitor: runs
src/main.py - Race monitor → API client: requests feed
src/main.py - Race monitor → Race series: selects series
src/main.py - Race monitor → Flag states: formats flags
src/main.py - Race monitor → Terminal colors: colors output
src/main.py - API client → NASCAR feed service: fetches feeds
src/ApiClient.py - API client → Operations feed: parses operations
src/ApiClient.py - API client → Live race feed: parses live data
src/ApiClient.py - API client → Race series: selects feed URL
src/ApiClient.py - Live race feed → Flag states: parses flag state
src/LiveFeed.py - Live race feed → Vehicle data: builds vehicles
src/LiveFeed.py - Vehicle data → Pit stop data: builds pit stops
src/Vehicle.py