openstack
/
project-config
Code Issues Proposed changes

Update update_constraints for Py3.8 

Most packages don't declare py38 support yet but the
upper-constraints.txt file does. This currently leads to propose changes
that update python 3.6 and 3.7 but not 3.8 entries. Special treat 3.8.

This follows https://review.opendev.org/719346.
It fixes https://review.opendev.org/#/c/719692/1/upper-constraints.txt

Change-Id: Id6bd791b7d9d5fc4daf7b4a9d92e7e4bd6bcbb19
This commit is contained in:
Andreas Jaeger 2020-04-15 14:55:38 +02:00
parent 0f896160f5
commit 14d4a0ff75
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
roles/copy-release-tools-scripts/files/release-tools/update_constraints.sh
View File

@ -113,6 +113,12 @@ else
sed -e "s/^${dist_name}=.*;python_version=='$PYTHON_VERSION'/$dist_name===$VERSION;python_version=='$PYTHON_VERSION'/" --in-place upper-constraints.txt
sed -e "s/^${canonical_name}=.*;python_version=='$PYTHON_VERSION'/$canonical_name===$VERSION;python_version=='$PYTHON_VERSION'/" --in-place upper-constraints.txt
done
# Most projects don't declare Python 3.8 support yet, so update if the
# package declares Python 3.6 support. This follows the logic that
# generate-constraints does
if [[ $PYTHON_3_VERSIONS =~ '3.6' ]] ; then
sed -e "s/^${dist_name}=.*;python_version=='3.8'/$dist_name===$VERSION;python_version=='3.8'/" --in-place upper-constraints.txt
fi
# Then only update lines that do not have specific python_versions
# specified.
sed -e "s/^${dist_name}=.*[0-9]$/$dist_name===$VERSION/" --in-place upper-constraints.txt