Unpinned tox test environment uses the last release of the project itself.
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Here we are trying to fetch the latest release of the all the base requirements and the last release of package itself. Is the intent here to test the last release of the package with no pins, or the current main branch with no pins (or we should be doing both)?
The failures at https://github.com/scipp/ess-project?tab=readme-ov-file#ess are for packages which have no releases on pypi yet.
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 with template/tox.ini.jinja lines 15-19 and inspect how the tox environment resolves the project and its base requirements. Review the linked ESS failures, then define whether the environment should test the latest release, the current main branch, or both, including projects without a PyPI release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100