django-haystack / django-haystack/celery-haystack
Programmatically disable signal handler(s)?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 226
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100