-
Notifications
You must be signed in to change notification settings - Fork 1.1k
LANG C.UTF-8 issue status? #887
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
Comments
Yeah, we should probably update to link to the latest failed attempt to remove it (#570, I think). The failures there make me very hesitant to try again without concrete evidence that we won't create similar problems again. |
edmorley
added a commit
to heroku/buildpacks-python
that referenced
this issue
Dec 16, 2024
Previously the buildpack would set the `LANG` env var at build and run time to the value `C.UTF-8`, to match the official Docker Python images. However, the env var should not be needed for modern Python, and so the official Docker Python images no longer set it: docker-library/python#887 docker-library/python#895 In addition, the older issues typically only affected other distros such as alpine, or environments where someone had overridden the system locale, which doesn't apply to the Heroku base images.
edmorley
added a commit
to heroku/buildpacks-python
that referenced
this issue
Dec 16, 2024
Previously the buildpack would set the `LANG` env var at build and run time to the value `C.UTF-8`, to match the official Docker Python images. However, the env var should not be needed for modern Python, and so the official Docker Python images no longer set it: docker-library/python#887 docker-library/python#895 In addition, the older issues typically only affected other distros such as alpine, or environments where someone had overridden the system locale, which doesn't apply to the Heroku base images. GUS-W-17443565.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I've noticed that almost every image on here has these lines defined:
It looks like the linked issue was closed back in 2017 and it might not be relevant anymore. I'm curious: are there any particular reasons to keep this around?
EDIT: Just saw that there was a failed attempt to remove
LANG
before — however, the cause of those errors seems unclear and we're still linking to an issue that has been closed/resolved for several years.The text was updated successfully, but these errors were encountered: