Update the Python 3.4.10 build script to use the correct Python version #1048
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The existing Python 3.4.10 archive actually contained Python 3.7.2, since the version in the source URL was not updated when the file was created in #813.
The build formula now uses the shared build script approach like all of the other build scripts, which ensures the version can never get out of sync (since it's extracted from the formula filename).
The build for Heroku-18 failed to compile
_ssl
properly (even though the build exited zero) since Python 3.4.10 is old enough it doesn't work well with libssl1.1. Installinglibssl1.0-dev
in the build image locally resolved the issue - however we don't want to use that in the future for newer Python, so I've not updated theheroku-18.Dockerfile
.In addition, with the rebuilt archives the tests now pass on Cedar-14, so no longer need to be marked as failing.
(There are a few other build scripts that need to be switched to the shared script approach, but they are being handled in the separate #1049, since those versions don't need anything to be rebuilt.)
Closes @W-7947035@.