use pkgutil.resolve_name in unittest.mock

Open
#88,852 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
testing

Research direction

The issue concerns name resolution in unittest.mock and references pkgutil.resolve_name; start by reviewing the relevant unittest.mock entry point and the pkgutil.resolve_name API. The existing pull request is the next place to inspect, and done means unittest.mock uses the requested resolver without changing its expected behavior.

Written by the indexing model from the issue text.

Description

3.11 stdlib
BPO 44686
Nosy @graingert, @miss-islington, @ukarroum
PRs
  • python/cpython#18544
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
closed_at = None
created_at = <Date 2021-07-20.19:29:08.426>
labels = ['3.11']
title = 'use pkgutil.resolve_name in unittest.mock'
updated_at = <Date 2022-01-21.09:11:29.429>
user = 'https://github.com/graingert'

    bugs.python.org fields:

    activity = <Date 2022-01-21.09:11:29.429>
actor = 'ukarroum'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2021-07-20.19:29:08.426>
creator = 'graingert'
dependencies = []
files = []
hgrepos = []
issue_num = 44686
keywords = []
message_count = 3.0
messages = ['397905', '397940', '411100']
nosy_count = 3.0
nosy_names = ['graingert', 'miss-islington', 'ukarroum']
pr_nums = ['18544']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue44686'
versions = ['Python 3.11']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    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/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.