Ensure backwards compatibility with recommended packages
Open
Nobody has claimed this yet.
tests
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 31899 |
|---|---|
| Nosy | @ncoghlan |
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 2017-10-30.05:23:17.468>
labels = ['3.7', '3.8', 'type-feature', 'tests']
title = 'Ensure backwards compatibility with recommended packages'
updated_at = <Date 2020-06-28.07:17:27.745>
user = 'https://github.com/ncoghlan'
bugs.python.org fields:
activity = <Date 2020-06-28.07:17:27.745>
actor = 'ncoghlan'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2017-10-30.05:23:17.468>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 31899
keywords = []
message_count = 2.0
messages = ['305211', '372502']
nosy_count = 1.0
nosy_names = ['ncoghlan']
pr_nums = []
priority = 'low'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31899'
versions = ['Python 3.7', 'Python 3.8']
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 reviewing the linked BPO issue 31899 and the CPython tests related to recommended packages; no specific file or test is named in this issue. Determine the backwards-compatibility cases that need coverage, then add tests demonstrating that the recommended packages continue to work as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100