Skip to content

Stop propagation makes events non-reusable #18

Description

@hartym

Although we may not want to change the current behaviour that can make sense in some cases, there are cases where the same event instance may need to be dispatched more than once, and it may be necessary to stop propagation in an intermediate listener.

Maybe add a reuse=True to dispatch/adispatch ? or ... ??

Activity

  1. added a commit that references this issue on Jun 5, 2026
    3d98360
  2. hartym commented on Jun 5, 2026

    @hartym
    MemberAuthor

    For 2.x this is addressed with a non-breaking, opt-in Event.reset() that clears propagation_stopped so the same instance can be dispatched again. PR #23.

    Resetting propagation at the start of every dispatch (reusable by default) is a behaviour change, so it is tracked separately for 3.0 in #24.

  3. modified the milestones: 3.x, 2.x on Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions