add configure option to control the groups of .pyc files to install
Open
Nobody has claimed this yet.
3.11
build
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44097 |
|---|---|
| Nosy | @gpshead, @tiran, @pxinwr |
| 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 2021-05-10.07:42:30.095>
labels = ['type-feature', 'build', '3.11']
title = 'add configure option to control the groups of .pyc files to install'
updated_at = <Date 2021-05-10.08:11:29.783>
user = 'https://github.com/pxinwr'
bugs.python.org fields:
activity = <Date 2021-05-10.08:11:29.783>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2021-05-10.07:42:30.095>
creator = 'pxinwr'
dependencies = []
files = []
hgrepos = []
issue_num = 44097
keywords = []
message_count = 3.0
messages = ['393356', '393363', '393365']
nosy_count = 3.0
nosy_names = ['gregory.p.smith', 'christian.heimes', 'pxinwr']
pr_nums = ['23920']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue44097'
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 reviewing PR python/cpython#23920 and the Build component's configure handling. The issue names no source file or test, so first identify the relevant build entry points and the intended groups of .pyc files. Done means the configure option controls which groups are installed as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100