Skip to content

Conversation

@lysnikolaou
Copy link
Member

Not sure if people are okay with using uv on Github Actions. If not, I can always just use pip instead.

@lysnikolaou lysnikolaou force-pushed the remove-tox branch 3 times, most recently from ec300f0 to 3715ce5 Compare October 13, 2025 17:10
Copy link
Contributor

@ngoldbaum ngoldbaum left a comment

Choose a reason for hiding this comment

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

Makes sense. I like that this moves a bunch of configuration out of the pyproject.toml file. I don't really think it adds much to force everyone who wants to run the tests locally to use coverage.

There's also a "Contributing" section in the readme that mentions tox that needs to be updated. I'd include a suggested test command since now it's not so obvious how to get the coverage info.

python-version: ['3.9', '3.10', '3.11', '3.12', '3.13', '3.13t', '3.14', '3.14t']
with-psutil: [false]
include:
- python-version: '3.13'
Copy link
Contributor

Choose a reason for hiding this comment

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

Does this need to be running on 3.13 for some reason? Otherwise I'd move it to 3.14(t).

@rgommers
Copy link
Member

👍🏼 from me as well

Not sure if people are okay with using uv on Github Actions.

uv is better maintained and has a nice UX, so I don't see any reason to not use it, 👍🏼👍🏼 from me

@lysnikolaou lysnikolaou merged commit 537d226 into Quansight-Labs:main Oct 21, 2025
10 checks passed
@lysnikolaou lysnikolaou deleted the remove-tox branch October 21, 2025 09:35
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.

3 participants