Looking to Contribute - What Should I Work On?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
No file, test, or entry point is specified. Start by reviewing the repository's contributing guidelines and open issues, then choose one narrowly scoped task such as a documented example or a reported bug; done should be defined by that selected issue's acceptance criteria.
Written by the indexing model from the issue text.
Description
Hi Attrs team!
I'm a young Python developer from Bangalore interested in contributing
to Attrs.
I've been contributing to Python open source libraries and would like
to help improve Attrs.
My GitHub: https://github.com/Aadhithyavarman-Techan
I've read your contributing guidelines and understand your code style
and testing requirements.
Why Attrs?
Attrs makes defining Python classes clean and powerful! I want to help
make it even better and more accessible to developers!
I'm interested in working on:
- New decorators - Adding new class definition features
- Documentation improvements - Adding more examples
- Performance optimization - Making Attrs faster
- Type hint improvements - Better type support
- Bug fixes - Fixing reported issues
Questions for the team:
- Are there any "good first issue" items you'd recommend?
- What areas would be most helpful right now?
- Any features on the roadmap that need help?
I'm committed to:
✓ Writing comprehensive tests
✓ Following your code style exactly
✓ Updating documentation
✓ Being responsive to feedback
Looking forward to contributing!
GitHub: @Aadhithyavarman-Techan
- Dominant language
- Python
- Stars
- 5.8k
- Forks
- 480
- Avg merge
- 2h 15m
- Merged PRs (30d)
- 2
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.
More from python-attrs/attrs
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
python-attrs/attrs#1596 · 2 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
python-attrs/attrs#1549 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
python-attrs/attrs#1543 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
python-attrs/attrs#1532 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
python-attrs/attrs#1500 · 1 comment ·
All issues in python-attrs/attrs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·