`library` folder not included in the source distribution
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- build-system
Research direction
Reproduce the failure with pipx and raven report --format raw, then inspect the package manifest and setuptools configuration for how the library folder is included. Build a source distribution and verify that its archive contains library; confirm the reproduced command no longer reports the missing-folder error.
Written by the indexing model from the issue text.
Description
Describe the bug
The library folder is not included in the source distribution built and sent to Pypi:
$ tar tf raven_cycode-1.0.9.tar.gz |grep library | wc -l
0
Thus, when installing raven-cycode using pip and the pypi repository, the library folder isn't available and causes certain commands to fail:
$ raven report --format raw
2024-06-04 14:31:42 | ERROR | [Errno 2] No such file or directory: 'library'
To Reproduce
$ pipx install raven-cycode
$ raven report --format raw
Expected behavior
The library folder should be shipped in the source distribution by including them in the package's manifest and by instructing setuptools to include package data during installation. To my knowledge, this is possible only by moving the library folder into the source package tree, otherwise it will likely pollute the Python library namespace.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- Fedora 39
- Python 3.12.3
- Raven 1.0.9
Additional context
Side note, currently the package used the folder src in the Python package namespace, which is also confusing. I suggest it to be renamed to something like raven if it doesn't conflict with other packages namespaces, at least less likely than src.
- Dominant language
- Python
- Stars
- 748
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
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 CycodeLabs/raven
-
报错 Open
Difficulty 4/5 3-5 days Newbie friendliness 15/100
CycodeLabs/raven#199 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
CycodeLabs/raven#188 · 2 comments · 1 reaction ·
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 25/100
CycodeLabs/raven#119 · 6 comments ·
-
feature indexer
Difficulty 3/5 1-2 days Newbie friendliness 45/100
CycodeLabs/raven#114 ·
-
downloader feature good first issue
Difficulty 3/5 1-2 days Newbie friendliness 25/100
CycodeLabs/raven#109 · 2 comments · 1 reaction ·
All issues in CycodeLabs/raven
Similar issues
-
bug ci good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
documentation
Difficulty 2/5 Half a day Newbie friendliness 62/100
inmanta/inmanta-core#10835 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
sponsored
Difficulty 2/5 1-3 hours Newbie friendliness 65/100