Difficulties in packaging

Open
#138 7 comments 0 reactions 0 assignees View on GitHub

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 testing optional dependency to be as minimal as possible. Other developer's dependencies like pytest-cov could be moved to test-cov optional dependency. Other dependencies that we are patching out: pytest-checkdocs, pytest-mypy, pytest-ruff. pytest-enabler is also disabled, but it might be good to add it eventually.
  • avoid or document the reason behind the lower-bound dependencies, e.g. setuptools>=61 is 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jaraco/skeleton

All issues in jaraco/skeleton

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.