Programmatically disable signal handler(s)?

Open
#39 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by searching the celery_haystack source for signal registrations and their callable names. Confirm whether .connect() and .disconnect() can target those handlers, then document the supported way to disable them.

Written by the indexing model from the issue text.

Description

Not a bug, more of a question. Is there a way to disable the celery_haystack signal handlers using the .connect()/.disconnect() methods? I know how to do this for signals I've written myself, but couldn't find the actual callable names in your source.

Dominant language
Python
Stars
226
Forks
95
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from django-haystack/celery-haystack

All issues in django-haystack/celery-haystack

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.