Skip to content

feat: adding force include#1238

Draft
henryiii wants to merge 1 commit intomainfrom
henryiii/feat/force-include
Draft

feat: adding force include#1238
henryiii wants to merge 1 commit intomainfrom
henryiii/feat/force-include

Conversation

@henryiii
Copy link
Copy Markdown
Collaborator

First draft of force-include, with the help of copilot in VSCode.

@henryiii henryiii force-pushed the henryiii/feat/force-include branch from 31d972b to 39312ce Compare February 26, 2026 20:58
Signed-off-by: Henry Schreiner <henryfs@princeton.edu>
@henryiii henryiii force-pushed the henryiii/feat/force-include branch from 39312ce to e3c1e02 Compare February 26, 2026 21:34
Destination path inside the SDist.

Leave empty to skip adding this source to the SDist.
"""
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having each item like this just to support writing to either sdist or wheel seems messy for more items that are added. Hatch's format seems better.

We could either flip the order like in hatch and make them force-inclued.(sdist|wheel) each being a dict, or we keep just the one key force-include and if they want to specify differently for sdist or wheel then we have the overrides mechanism that can already do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants