Skip to content

chore: migrate from setup tools to hatchling#881

Open
Jo-Byr wants to merge 1 commit into
masterfrom
hatchling
Open

chore: migrate from setup tools to hatchling#881
Jo-Byr wants to merge 1 commit into
masterfrom
hatchling

Conversation

@Jo-Byr
Copy link
Copy Markdown

@Jo-Byr Jo-Byr commented Apr 21, 2026

Migrate from setup tools to hatchling, related to #842

@Jo-Byr Jo-Byr requested a review from jourdain April 21, 2026 13:22
@jourdain
Copy link
Copy Markdown
Collaborator

We should move the src code under a ./src/ directory.

@Jo-Byr
Copy link
Copy Markdown
Author

Jo-Byr commented Apr 24, 2026

We should move the src code under a ./src/ directory.

So simply move the trame directory under a src folder without further modifications ?

@jourdain
Copy link
Copy Markdown
Collaborator

I think so, I mean you need to update the pyproject to reflect that.
You can look at https://github.com/Kitware/trame-common/blob/main/pyproject.toml just to make sure you see how the src directory is affecting the pyproject.

Comment thread proxy-mapping.txt Outdated
Comment thread src/trame/LICENSE Outdated
@jourdain
Copy link
Copy Markdown
Collaborator

Looks reasonable. Does it work when you run uv build?

@Jo-Byr
Copy link
Copy Markdown
Author

Jo-Byr commented May 15, 2026

Does it work when you run uv build?

Yes

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