Summary

Move the event scheduling functionality from mesa.experimental.devs.eventlist to a new stable mesa.time module. This stabilizes the event-based simulation system that was introduced experimentally and makes it a first-class feature of Mesa.

Also renames SimulationEvent to Event.

Motive

The event scheduling system (EventList, SimulationEvent, EventGenerator, Schedule, Priority) has been in experimental status since its introduction. After extensive testing and usage, it's ready to be stabilized and made part of Mesa's core API. This promotes better time management in agent-based models and supports both discrete event simulation and hybrid approaches.

Usage Examples

The event scheduling system can now be imported from the stable namespace:

from mesa.time import EventList, SimulationEvent, Priority, Schedule, EventGenerator

# Schedule a one-time event
model.schedule_event(my_function, at=5.0, priority=Priority.HIGH)

# Schedule recurring events
schedule = Schedule(interval=1.0, start=0.0)
model.schedule_recurring(my_function, schedule, priority=Priority.DEFAULT)

# Use event generators for complex recurring patterns
generator = EventGenerator(model, my_function, schedule).start()

All existing functionality remains unchanged, this is purely a reorganization to stabilize the API.

Additional Notes

• This is a non-breaking change for users already using the experimental API (imports from mesa.experimental.devs.eventlist still work via the simulator module's imports)
• The Simulator classes remain in experimental status (and will be deprecated and removed in follow-up PRs)
• All tests pass with updated imports
• Documentation has been updated to reflect the new stable location
• Follows Mesa's deprecation policy by providing the alternative before any deprecation warnings

Follows #3201, #3204 and #3266, discussed in #2921, part of #3132.