Partially specializing default plugin hooks

Open
#3,591 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reading the linked pull request discussion and the existing user-plugin and default-plugin hook behavior. Determine how hooks are selected and what a dynamic fallback would need to preserve; done would be a documented, tested mechanism for a user hook to delegate to the default hook.

Written by the indexing model from the issue text.

Description

needs discussion priority-2-low topic-plugins

@gvanrossum said in https://github.com/python/mypy/pull/3534#discussion_r123368850:

So a user plugin can override the default plugin. Should a hook returned by a user plugin be able to fall back dynamically on the default plugin's hook for the same function? E.g. suppose to add a special case for open() I would have to copy the default open() handler and modify it. It would be nice if there was some kind of "super call" mechanism for this.

Dominant language
Python
Stars
20.6k
Forks
3.3k
Avg merge
1d 18h
Merged PRs (30d)
54

Contributor guide

Open the contributing guide

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 python/mypy

All issues in python/mypy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.