python / python/importlib_metadata
Consider reverting optimization in normalization
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 142
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Description
In https://github.com/python/importlib_metadata/issues/533#issuecomment-4099281201_, I got the impression that the optimization may be premature. Now that code bases have stabilized and the performance checks are more precise, let's revisit 3e7f3ac6742a63ab729966c0ff8e205f92ac42f7 and decide if it's really worth the complication.
Contributor guide
No contributing guide indexed for this repository
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 the discussion in issue #533 and inspecting commit 3e7f3ac6742a63ab729966c0ff8e205f92ac42f7. Run the repository's performance checks and compare the optimization's benefit with its complication; done means reaching and documenting a decision on whether it should be reverted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100