Difficulties in packaging
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system
Research direction
Start by reviewing the skeleton's testing optional dependencies and the lower-bound dependencies used in its generated projects. Compare them with Fedora and EPEL9 packaging needs, including the listed pytest packages and setuptools>=61; done means the testing extra is minimal and dependency lower bounds are documented or adjusted.
Written by the indexing model from the issue text.
Description
Hi @jaraco I don't know the best place to contact you for this, but hopefully this would be a relevant place to do so.
I am trying to package some of your packages to Fedora (already packaged) and EPEL9, and most of your projects are derived from your skeleton repo and I have a few issues I would like to discuss if you could make some changes to make our lives a bit easier:
- separate
testingoptional dependency to be as minimal as possible. Other developer's dependencies likepytest-covcould be moved totest-covoptional dependency. Other dependencies that we are patching out:pytest-checkdocs,pytest-mypy,pytest-ruff.pytest-enableris also disabled, but it might be good to add it eventually. - avoid or document the reason behind the lower-bound dependencies, e.g.
setuptools>=61is unclear why this lower bound is used since PEP517 seems to have been available way before that.
This is particularly important because of the package importlib_resources that you are maintaining containing various fixes that need to be backported to lower python version and packaging to long-term distros including EPEL9.
- Dominant language
- No language data
- Stars
- 152
- Forks
- 38
- Avg merge
- 6h 27m
- Merged PRs (30d)
- 4
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/skeleton
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
0.kind: bug
Difficulty 1/5 Under an hour Newbie friendliness 82/100
NixOS/nixpkgs#588857 · 1 reaction ·
Maintainers usually reply within 1 day
-
area:ui bug effort:low P2 source:agent
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
MattiaPARRINELLO/backstage#71 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
untemps/svelte-palette#298 ·
-
Retarget the extension to Fallout 10.5Possibly taken @ChrisonSimtian claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100