Add optional weights to random.sample()
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40569 |
|---|---|
| Nosy | @tim-one, @rhettinger, @mdickinson, @Cryvate, @dhdavvie |
| PRs |
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-05-08.19:56:47.608>
labels = ['type-feature', 'library', '3.9']
title = 'Add optional weights to random.sample()'
updated_at = <Date 2020-05-10.09:06:35.481>
user = 'https://github.com/rhettinger'
bugs.python.org fields:
activity = <Date 2020-05-10.09:06:35.481>
actor = 'dheiberg'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-05-08.19:56:47.608>
creator = 'rhettinger'
dependencies = []
files = []
hgrepos = []
issue_num = 40569
keywords = ['patch']
message_count = 5.0
messages = ['368458', '368559', '368562', '368565', '368573']
nosy_count = 5.0
nosy_names = ['tim.peters', 'rhettinger', 'mark.dickinson', 'cryvate', 'dheiberg']
pr_nums = ['20014']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue40569'
versions = ['Python 3.9']
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 PR #20014 and the existing random.sample() entry point in Python's standard library. Determine the intended optional-weight behavior and confirm that the feature is complete when weighted sampling works without weights remaining backwards incompatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100