Update Tools/freeze to make use of Tools/scripts/freeze_modules.py?
Open
Nobody has claimed this yet.
3.11
build
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 45096 |
|---|---|
| Nosy | @malemburg, @ericsnowcurrently |
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-09-03.19:43:47.992>
labels = ['type-bug', '3.11']
title = 'Update Tools/freeze to make use of Tools/scripts/freeze_modules.py?'
updated_at = <Date 2021-10-27.15:45:43.297>
user = 'https://github.com/ericsnowcurrently'
bugs.python.org fields:
activity = <Date 2021-10-27.15:45:43.297>
actor = 'eric.snow'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Demos and Tools']
creation = <Date 2021-09-03.19:43:47.992>
creator = 'eric.snow'
dependencies = []
files = []
hgrepos = []
issue_num = 45096
keywords = ['patch']
message_count = 1.0
messages = ['401015']
nosy_count = 2.0
nosy_names = ['lemburg', 'eric.snow']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45096'
versions = ['Python 3.11']
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 reading Tools/freeze and Tools/scripts/freeze_modules.py, then compare how each currently performs the freezing work. Determine the changes needed for Tools/freeze to use freeze_modules.py, and verify that the updated tool preserves its existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100