Optional dependencies don't participate in extension invalidation

Open
  • Is something wrong?
#4,912 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@alejoe91 is already working on this.

Since Nov 5, 2026.

  • #4913 by @alejoe91 — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start with the linked photon-mosaic issue 182 for the original context, then trace where child dependencies are registered during import and how extension invalidation handles parameter-dependent dependencies. The open pull request 4913 indicates work is already underway; completion should cover invalidation when those dependencies change based on parameters.

Written by the indexing model from the issue text.

Description

bug core

See original issue on photon-mosaic: https://github.com/photon-mosaic/photon-mosaic/issues/182

TLDR; children dependencies are only registered at import time, failing to catch param-dependent dependencies

Dominant language
Python
Stars
870
Forks
284
Avg merge
3d 1h
Merged PRs (30d)
41

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 SpikeInterface/spikeinterface

All issues in SpikeInterface/spikeinterface

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.