Build using 'flit' version 4

Open Beginner friendly
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
build-system

Research direction

Start with pyproject.toml in jaraco/tempora and the build-system.requires = ["flit-core >=3.11, <4"] line the issue quotes. Read the flit 4.0 release notes/CHANGELOG to see what changed in flit-core 4 (config keys, metadata validation, build behaviour), then decide whether the upper bound can be dropped or widened. Done means the metadata builds cleanly: run flit build (or python -m build) locally with flit 4 installed and confirm an sdist and wheel are produced without warnings or errors.

Written by the indexing model from the issue text.

Description

The project metadata ('pyproject.toml') specifies build-system.requires = ["flit-core >=3.11, <4"]. Is that upper limit still relevant?

Flit version 4 was released in August this year (with version 4.0.1). What changes are needed in 'tempora' to have it build with the latest 'flit' release?

Dominant language
Python
Stars
23
Forks
15
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

  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/tempora

All issues in jaraco/tempora

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.