Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the Python 3.4.10 build script to use the correct Python version #1048

Merged
merged 1 commit into from
Aug 12, 2020

Conversation

edmorley
Copy link
Member

@edmorley edmorley commented Aug 12, 2020

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. Installing libssl1.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 the heroku-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@.

@edmorley edmorley added the bug label Aug 12, 2020
@edmorley edmorley requested a review from a team as a code owner August 12, 2020 12:04
@edmorley edmorley self-assigned this Aug 12, 2020
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. Installing `libssl1.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 the `heroku-18.Dockerfile`.

In addition, with the rebuilt archives the tests now pass on Cedar-14,
so no longer need to be marked as failing.

Closes @W-7947035@.
@edmorley edmorley merged commit eabe71d into main Aug 12, 2020
@edmorley edmorley deleted the fix-python-3.4.10 branch August 12, 2020 14:19
dryan pushed a commit to dryan/heroku-buildpack-python that referenced this pull request Nov 19, 2020
…on (heroku#1048)

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 heroku#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. Installing `libssl1.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 the `heroku-18.Dockerfile`.

In addition, with the rebuilt archives the tests now pass on Cedar-14,
so no longer need to be marked as failing.

Closes @W-7947035@.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants