Migrate to `hatch-cpp`

Open
  • Is something wrong?
#584 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, python
Domain
build-system, developer-experience

Research direction

Read the hatch-cpp project first, then inspect the repository's Makefile and setup.py, including the linked examples. Determine how the current scikit-build setup is used and what hatch-cpp requires; done means the project is migrated and local development is easier as described.

Written by the indexing model from the issue text.

Description

part: build tag: internal type: feature

https://github.com/python-project-templates/hatch-cpp

hatch-cpp removes our reliance on old scikit-build and should make it much easier to develop locally, making it easier to do things like this and this.

Its not quite ready, but will be soon at which point we should move to it to improve developer experience

Dominant language
Python
Stars
450
Forks
91
Avg merge
18h 8m
Merged PRs (30d)
3

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 Point72/csp

All issues in Point72/csp

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.