Skip to content

chore: migrate from setup tools to hatchling#78

Merged
jourdain merged 1 commit intoKitware:masterfrom
Jo-Byr:hatchling
May 2, 2026
Merged

chore: migrate from setup tools to hatchling#78
jourdain merged 1 commit intoKitware:masterfrom
Jo-Byr:hatchling

Conversation

@Jo-Byr
Copy link
Copy Markdown
Contributor

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

No description provided.

@Jo-Byr Jo-Byr force-pushed the hatchling branch 2 times, most recently from 06f1fe3 to e403696 Compare April 21, 2026 13:06
@jourdain
Copy link
Copy Markdown
Collaborator

Can you move the code under a src/ directory.

@Jo-Byr
Copy link
Copy Markdown
Contributor Author

Jo-Byr commented Apr 24, 2026

Can you move the code under a src/ directory.

Should I create a "trame" directory as is done on other trame projects ? Considering this project has a different structure, I suppose we wouldn't have anything to serve under "widgets", do we want to server what's currently under trame_server under trame.modules.server ?

@jourdain
Copy link
Copy Markdown
Collaborator

No that one should only have ./src/trame_server/*. The trame namespace is for widgets, ui, tools, in this case we don't want to act as a plugin. The trame repo already pickup the classes it needs from the server and expose them where it matter.

@Jo-Byr
Copy link
Copy Markdown
Contributor Author

Jo-Byr commented Apr 28, 2026

@jourdain it should be good now

@jourdain jourdain merged commit e14b029 into Kitware:master May 2, 2026
5 checks passed
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