Package install omits required package data file 'irc/codes.txt'
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system
Research direction
The crash starts in irc/events.py at line 68, where _codes is read via lines_from, and irc/tests/test_bot.py reproduces it. Check how the build declares package data in the project's packaging configuration, so that irc/codes.txt ends up in the built package. Done when a freshly built wheel contains irc/codes.txt and the test module imports and runs.
Written by the indexing model from the issue text.
Description
The 'irc/codes.txt' file is not installed to the package. This results in a crash when the library attempts to read this package data file.
For example, the test suite fails:
$ python3 -m pytest irc/tests/test_bot.py
============================= test session starts ==============================
[…]
==================================== ERRORS ====================================
_________________________ ERROR collecting irc/bot.py __________________________
irc/bot.py:16: in <module>
import irc.client
irc/client.py:72: in <module>
from . import connection, ctcp, events, features, message, schedule
irc/events.py:68: in <module>
numeric = {code.code: code for code in _codes}
^^^^^^
/usr/lib/python3/dist-packages/jaraco/text/__init__.py:643: in lines_from
with input.open(encoding='utf-8') as stream:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
/usr/lib/python3.14/pathlib/__init__.py:772: in open
return io.open(self, mode, buffering, encoding, errors, newline)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
E FileNotFoundError: [Errno 2] No such file or directory: '/build/reproducible-path/python-irc-20.5.0+dfsg1/.pybuild/cpython3_3.14_irc/build/irc/codes.txt'
[…]
- Dominant language
- Python
- Stars
- 422
- Forks
- 91
- 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 jaraco/irc
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
CTCP ISSUEOpen
Difficulty 1/5 Under an hour Newbie friendliness 55/100
Similar issues
-
area:cli area:security bug priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
docs pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#13563 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
NCATSTranslator/Babel#1204 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
alltheplaces/alltheplaces#20570 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
sio2project/oioioi#981 · 1 reaction ·
Maintainers usually reply within 1 day