Skip to content

Fix the security update version check message for PyPy#1040

Merged
edmorley merged 1 commit intomainfrom
fix-eol-pypy-message
Aug 11, 2020
Merged

Fix the security update version check message for PyPy#1040
edmorley merged 1 commit intomainfrom
fix-eol-pypy-message

Conversation

@edmorley
Copy link
Copy Markdown
Member

@edmorley edmorley commented Aug 11, 2020

Previously if an app was using an older version of PyPy, the buildpack would show a confusing "Could not find that version" message (even though the version was found), when it really meant to warn about there being a newer release available.

It looks like the version check messages were perhaps copied and pasted from something else, but the message wording not updated at the time.

I've also added tests since there were none for this feature.

Longer term the entire security update version check feature could do with a refactor to avoid the repetition, however this at least fixes the broken behaviour for now.

Fixes #1004.
Closes @W-7918745@.

Previously if an app was using an older version of PyPy, the buildpack
would show a confusing "Could not find that version" message (even
though the version was found), when it really meant to warn about there
being a newer release available.

It looks like the version check messages were perhaps copied and pasted
from something else, but the message wording not updated at the time.

Fixes #1004.
Closes @W-7918745@.
@edmorley edmorley requested a review from a team as a code owner August 11, 2020 12:50
@edmorley edmorley self-assigned this Aug 11, 2020
@edmorley edmorley merged commit f508bd5 into main Aug 11, 2020
@edmorley edmorley deleted the fix-eol-pypy-message branch August 11, 2020 18:15
dryan pushed a commit to dryan/heroku-buildpack-python that referenced this pull request Nov 19, 2020
Previously if an app was using an older version of PyPy, the buildpack
would show a confusing "Could not find that version" message (even
though the version was found), when it really meant to warn about there
being a newer release available.

It looks like the version check messages were perhaps copied and pasted
from something else, but the message wording not updated at the time.

I've also added tests since there were none for this feature.

Fixes heroku#1004.
Closes @W-7918745@.
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.

Outdated Python version check message is incorrect for PyPy

2 participants