microsoft / microsoft/MegaDetector
Remove duplicate src/megadetector_ai package (canonical is megadetector_core)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 50
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Summary
The repo currently tracks two Python packages under src/ with identical file sets:
src/megadetector_core/— canonical; the installed entry point ismegadetector = "megadetector_core.cli:main"(seepyproject.toml,name = "megadetector-core").src/megadetector_ai/— a duplicate (__init__.py,cli.py,detector.py,training.py,training_utils.py) that is not referenced by the project entry point.
Why this matters
- The two copies can silently diverge; bug fixes/edits to one won't reach the other.
- Contributors and documentation can reference the wrong namespace.
- Increases package size and confusion for anyone reading
src/.
Proposed action
- Confirm
megadetector_aihas no remaining importers/entry points. - Remove
src/megadetector_ai/(or, if it is intentionally retained, document why and de-duplicate the shared code).
Notes
Surfaced during a documentation/SEO pass; all new docs reference megadetector_core only. Tracking-only issue — no code change required from the docs work.
Contributor guide
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 repository for imports or entry points referencing src/megadetector_ai/. Read pyproject.toml to confirm megadetector_core is the canonical package and inspect the duplicate file set listed in the issue. Done means no remaining references or entry points depend on megadetector_ai and the duplicate directory is removed, or its retention is documented with a clear reason.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience, tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100