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.

Sign up for GitHub

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

Jump to bottom

Improve the wording of the Python 2.7 EOL error message #1367

Merged
merged 2 commits into from
Sep 28, 2022
Merged

Improve the wording of the Python 2.7 EOL error message #1367

merged 2 commits into from
Sep 28, 2022

Conversation

edmorley
Copy link
Member

To make the call to action clearer - since there have been a couple of support tickets that show people didn't know what to do, even with the FAQ link.

GUS-W-11821872.

@edmorley
Improve the wording of the Python 2.7 EOL error message (#1367)
6142d60 
To make the call to action clearer - since there have been a couple
of support tickets that show people didn't know what to do, even
with the FAQ link.

GUS-W-11821872.
@edmorley edmorley self-assigned this Sep 28, 2022
@edmorley edmorley force-pushed the clarify-python-2.7-error branch from 1ab3411 to 4c000c3 Compare September 28, 2022 07:31
@edmorley edmorley marked this pull request as ready for review September 28, 2022 07:33
@edmorley edmorley requested a review from a team as a code owner September 28, 2022 07:33
@edmorley edmorley changed the title Improve the wording of the Python 2.7 EOL error message (#1367) Improve the wording of the Python 2.7 EOL error message Sep 28, 2022
@edmorley edmorley merged commit e81cf0e into main Sep 28, 2022
@edmorley edmorley deleted the clarify-python-2.7-error branch September 28, 2022 07:38
edmorley added a commit that referenced this pull request Sep 28, 2022
@edmorley
Improve the wording of the Python 2.7 EOL error message (#1367)
2f52fe0 
To make the call to action clearer - since there have been a couple
of support tickets that show people didn't know what to do, even
with the FAQ link.

GUS-W-11821872.
@edmorley
Copy link
Member Author

Released:

$ make publish
Deploy as version: v220 [y/n]? y

Tagging commit e81cf0e0678fa0c6ff51b02bcc1be216b934d3b4 with v220... 
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To https://github.com/heroku/heroku-buildpack-python
 * [new tag]         v220 -> v220

Publishing to the buildpack registry...
Two-factor code: ********************************************
Publishing buildpack heroku/python... done
Publishing buildpack was successful

Version  Released At               Status
───────  ────────────────────────  ─────────
220      2022-09-28T07:38:41.725Z  published

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Malax Malax Malax approved these changes

Assignees

@edmorley edmorley

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@edmorley @Malax