Benefits Denial/unfair.py's top-of-file proxy summary still claims Native applicants are at "~15%" high-skill-role rate (actual: 20.3%) - #704 only fixed the bottom section
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 95/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Open Benefits Denial/unfair.py and compare the top-of-file header comment with the corrected “WHAT'S WRONG” section below it. Run python3 "Benefits Denial/unfair.py" and the provided grep commands to verify the reported percentages. Done means the header distinguishes Black applicants (~15.5%) from Native applicants (20.3%) and no longer claims both are ~15%.
Written by the indexing model from the issue text.
Description
Where: Benefits Denial/unfair.py, the top-of-file header comment block (vs. the already-corrected text further down in the same file).
The gap: Commit 30a8042 (closing issue #704) fixed the "WHAT'S WRONG" printed section to correctly distinguish Black applicants (~15.5% of high-skill roles, about half White's 26.2%) from Native applicants (20.3%, ~77% of White's rate). But the identical, unfixed claim still exists earlier in the same file's header comment block:
# occupation → Racial occupational segregation: Black and
# Native applicants are in high-skill roles
# at ~15% vs 26% for White applicants.
This still lumps Native in with Black's ~15% figure, contradicting both the real data and the file's own already-corrected text further down.
Repro:
python3 "Benefits Denial/unfair.py" | grep -A5 "high-skill occupations by race"
# Amer-Indian-Eskimo 20.3%
# Asian-Pac-Islander 30.9%
# Black 15.5%
# Other 15.5%
# White 26.2%
grep -n "Native applicants are in high-skill roles" "Benefits Denial/unfair.py" # stale "~15%"
grep -n "20.3%, ~77% of White" "Benefits Denial/unfair.py" # already-corrected figure
Fix direction: Update the header comment to match the already-corrected text below it - split out Black (~15.5%, about half White's) from Native (20.3%, ~77% of White's) instead of lumping both at "~15%".
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 99
Getting set up
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.
More from yakew7/Fair-Code
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
docs pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
pydantic/pydantic-ai#8863 ·
Maintainers usually reply within 1 day
-
documentation from-review-extraction github-actions priority: low severity:nit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
LearningCircuit/local-deep-research#6946 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
esphome/device-builder#2856 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
mantinedev/mantine#9223 ·
Maintainers usually reply within 6 days