[Bug] `requirements-dev.txt` misses dependencies needed for local Python tests
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 396
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.
### Paimon version
`paimon-python/dev/requirements-dev.txt` is currently incomplete for local Python development. For example, basic test dependencies such as pytest are not fully represented there, so developers cannot rely on this file to set up a local environment for running Python tests.
As a result, local setup has to be inferred from the GitHub CI workflow, where many dependencies are installed manually in `.github/workflows/paimon-python-checks.yml`. This makes local development error-prone and easy to drift from CI.
### Compute Engine
Not related
### Minimal reproduce step
- Create a clean virtualenv
- Running `pip install -r dev/requirements-dev.txt`
- Running `pytest`, a lot of dependencies are missing, including `pytest` itself
### What doesn't meet your expectations?
`requirements-dev.txt` should include the common dependencies needed for local Python test development. After that, CI can reuse this file for the common setup, while keeping feature-specific dependencies installed separately when needed.
### Anything else?
_No response_
### Are you willing to submit a PR?
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Compare paimon-python/dev/requirements-dev.txt with the dependencies installed in .github/workflows/paimon-python-checks.yml, starting with the clean-virtualenv reproduction described in the issue. Ensure the shared local test dependencies are covered and verify that pip install followed by pytest works; CI should be able to reuse the common setup while retaining feature-specific installs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, developer-experience, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100