[SPARK-31231][BUILD][FOLLOW-UP] Set the upper bound (before 46.1.0) for setuptools in pip package test
## What changes were proposed in this pull request? This PR is a followup of apache/spark#27995. Rather then pining setuptools version, it sets upper bound so Python 3.5 with branch-2.4 tests can pass too. ## Why are the changes needed? To make the CI build stable ## Does this PR introduce any user-facing change? No, dev-only change. ## How was this patch tested? Jenkins will test. Closes #28005 from HyukjinKwon/investigate-pip-packaging-followup. Authored-by: HyukjinKwon <gurwls223@apache.org> Signed-off-by: HyukjinKwon <gurwls223@apache.org>
This commit is contained in:
parent
336621e277
commit
178d472e1d
|
@ -76,7 +76,7 @@ for python in "${PYTHON_EXECS[@]}"; do
|
|||
VIRTUALENV_PATH="$VIRTUALENV_BASE"/$python
|
||||
rm -rf "$VIRTUALENV_PATH"
|
||||
if [ -n "$USE_CONDA" ]; then
|
||||
conda create -y -p "$VIRTUALENV_PATH" python=$python numpy pandas pip setuptools=46.0.0
|
||||
conda create -y -p "$VIRTUALENV_PATH" python=$python numpy pandas pip "setuptools<46.1.0"
|
||||
source activate "$VIRTUALENV_PATH"
|
||||
else
|
||||
mkdir -p "$VIRTUALENV_PATH"
|
||||
|
|
Loading…
Reference in a new issue