pytest-dev / pytest-dev/pytest-qt
Modernize/improve various development things
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 455
- Forks
- 72
- Avg merge
- 12h 26m
- Merged PRs (30d)
- 1
Description
I noticed a couple of things while picking up work on pytest-qt again:
- One test uses
tmpdirinstead oftmp_path - All tests use
testdirinstead ofpytester - We might want to switch from autoflake/pyupgrade/black/flake8 to ruff?
- We should switch from
setup.pyto apyproject.toml(and maybeuv?) - License PyPI classifiers are deprected, we should use a SPDX license
- We should force colored pytest output on GitHub Actions
- We should have type annotations and use mypy on CI (and then probably add
py.typedtoo)
Thoughts? We should probably split this into more bite-sized issues, just writing down what went through my head before I forget everything again.
Contributor guide
No contributing guide indexed for this repository
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 splitting the checklist into focused issues, then inspect the tests using tmpdir/testdir and the project’s setup.py and GitHub Actions configuration. Review the proposed pyproject.toml, tooling, licensing, output, and typing changes separately; done should mean each scoped modernization has an agreed implementation and passing CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, developer-experience, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100