python / python/cpython

pkg_resources seems to treat python 3.10 as python 3.1

Open
#86,910 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.10 topic-installation type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 42744
Nosy @tirkarthi, @RhinosF1

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 2020-12-25.19:35:20.899>
labels = ['type-bug', 'expert-installation', '3.10']
title = 'pkg_resources seems to treat python 3.10 as python 3.1'
updated_at = <Date 2021-02-10.17:22:42.696>
user = 'https://github.com/RhinosF1'

bugs.python.org fields:

activity = <Date 2021-02-10.17:22:42.696>
actor = 'RhinosF1'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Installation']
creation = <Date 2020-12-25.19:35:20.899>
creator = 'RhinosF1'
dependencies = []
files = []
hgrepos = []
issue_num = 42744
keywords = []
message_count = 5.0
messages = ['383760', '386789', '386790', '386792', '386794']
nosy_count = 2.0
nosy_names = ['xtreak', 'RhinosF1']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42744'
versions = ['Python 3.10']

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.

Research direction

Start by reproducing the pkg_resources behavior with Python 3.10 and locate the installation-related implementation and tests; the issue names no files or tests. Done means Python 3.10 is distinguished from Python 3.1 without regressing existing version handling. The migrated metadata records the underlying issue as fixed, so first verify whether any work remains.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.