UCL-ARC / UCL-ARC/python-tooling
Should we drop `tox`?
Open
Nobody has claimed this yet.
question
website
- Dominant language
- Python
- Stars
- 62
- Forks
- 10
- Avg merge
- 7d 6h
- Merged PRs (30d)
- 6
Description
What is the Topic of Your Question
Website and template
Add Your Question Below
It seems like we're almost all using uv and not really using tox for any new projects. Should we drop it from the website and template?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the website and project template references to tox, then compare them with the stated uv-based workflow. Resolve whether tox should be removed from both locations; done means the decision is documented and the affected references are updated consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100