Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

list_plugin_distinfo() keeps unregistered plugins

Open
#763 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@RonnyPfannschmidt is already working on this.

Since Oct 9, 2026.

  • #764 by @jovial-liu — closed without merging
  • #766 by @goudan789 — closed without merging
  • #767 by @RonnyPfannschmidt — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start in unregister() and in load_setuptools_entrypoints(), which appends to _plugin_distinfo, then check what list_plugin_distinfo() and list_plugin_distributions() return after a plugin is unregistered. Linked PR #764 was closed without merging, so read its discussion before starting. Done means unregistering a plugin removes its distinfo entries and re-registering it through entry points adds no duplicate.

Written by the indexing model from the issue text.

Description

🤖 Written by Claude Opus 5.5 via Claude Code for the pluggy maintainers; I prompted it, it did the work, I read it.

load_setuptools_entrypoints() appends to _plugin_distinfo, but unregister() never removes those entries. After unregistering, list_plugin_distinfo() and list_plugin_distributions() still list the plugin, and that list feeds pytest's "plugins:" header. Re-registering through entry points then adds a duplicate entry.

Confirmed by reading the code and a synthetic repro, not by a real entry-point load.

Proposal: drop the plugin's entries in unregister().

Found while working on #759.

Dominant language
Python
Stars
1.7k
Forks
172
Avg merge
2d 18h
Merged PRs (30d)
21

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 pytest-dev/pluggy

All issues in pytest-dev/pluggy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.