Paths should be repr'ed in exceptions
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems
Research direction
Start by locating the exception formatting for missing files and inspect how the path from the reported example is rendered. Confirm the desired representation for paths containing spaces, then add coverage for the exception message and verify that the path is shown in repr form.
Written by the indexing model from the issue text.
Description
E.g.: FileNotFound: No such file or directory: /Users/julian/Library/Application Support/great/config.toml
- Dominant language
- Python
- Stars
- 2
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 Julian/Filesystems
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Julian/Filesystems#51 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Julian/Filesystems#50 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Julian/Filesystems#45 ·
-
fs.chownOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
Julian/Filesystems#44 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Julian/Filesystems#43 ·
All issues in Julian/Filesystems
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Deltares/imod-python#1940 ·
Maintainers usually reply within 1 day
-
effort: low prio: low ready
Difficulty 1/5 Under an hour Newbie friendliness 82/100
digitalfabrik/integreat-cms#4621 ·
Maintainers usually reply within 5 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ioos/compliance-checker#1375 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
netbox status: backlog topic: testing type: housekeeping
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
netbox-community/netbox#23395 ·
Maintainers usually reply within 1 day