pytest-dev / pytest-dev/pytest
automatic tox env cachedir has no ux indication and triggers always
Open
Nobody has claimed this yet.
plugin: cache
type: bug
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
- #4270 introduced a potentially confusing/problematic behaviour of automnatically using a pytest cache in a tox env dir
that caused #8818 which was fixxed by a manual override
pytest should indicate when it picks different cache dirs and we should consider how to deal with tox is local vs tox is jsut used to invoke
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 reading issues #4270 and #8818 to understand the automatic pytest cache-directory behavior and its manual override. Then examine how pytest reports cache-directory selection when invoked through tox; done means the differing cache location is clearly indicated and the local-tox versus tox-invocation cases have an agreed handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100