-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
ref(py3): Make PY3 the default*, add SENTRY_PYTHON #763
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is in preparation to make the PY3 version the default for Docker images and self-hosted. It is part **2/5**: 1. Add `-py2` variants for the Python 2 bulid tags and introduce the `SENTRY_PYTHON2` env variable usage 2. **Switch getsentry/onpremise to Python 3 by default, introducing the `SENTRY_PYTHON2` env var for Py2 builds via the `-py2` suffix** 3. Move the unsuffixed version of the builds to Python 3 4. Remove the `SENTRY_PYTHON3` env var support and `-py3` prefix usage from getsentry/onpremise 5. Remove tagging of `-py3` builds from here Depends on getsentry/sentry#22460.
…too tricky" This reverts commit 0d11854.
chadwhitacre
approved these changes
Dec 4, 2020
BYK
added a commit
to getsentry/sentry
that referenced
this pull request
Dec 4, 2020
This is in preparation to make the PY3 version the default for Docker images and self-hosted. It is part **3/5**: 1. ~~Add `-py2` variants for the Python 2 build tags and introduce the `SENTRY_PYTHON2` env variable usage~~ (#22460) 2. ~~Switch getsentry/onpremise to Python 3 by default*, introducing the `SENTRY_PYTHON2` env var for Py2 builds via the `-py2` suffix~~ (getsentry/self-hosted#763) 3. **Move the unsuffixed version of the builds to Python 3** 4. Remove the `SENTRY_PYTHON3` env var support and `-py3` prefix usage from getsentry/onpremise 5. Remove tagging of `-py3` builds from here We should still have the `-py3` images, whcih will be the same with the images w/o the suffix.
BYK
added a commit
to getsentry/sentry
that referenced
this pull request
Dec 4, 2020
This is in preparation to make the PY3 version the default for Docker images and self-hosted. It is part **3/5**: 1. ~~Add `-py2` variants for the Python 2 build tags and introduce the `SENTRY_PYTHON2` env variable usage~~ (#22460) 2. ~~Switch getsentry/onpremise to Python 3 by default*, introducing the `SENTRY_PYTHON2` env var for Py2 builds via the `-py2` suffix~~ (getsentry/self-hosted#763) 3. **Move the unsuffixed version of the builds to Python 3** 4. Remove the `SENTRY_PYTHON3` env var support and `-py3` prefix usage from getsentry/onpremise 5. Remove tagging of `-py3` builds from here We should still have the `-py3` images, whcih will be the same with the images w/o the suffix.
BYK
added a commit
that referenced
this pull request
Dec 4, 2020
This is in preparation to make the PY3 version the default for Docker images and self-hosted. It is part **4/5**: 1. ~~Add `-py2` variants for the Python 2 build tags and introduce the `SENTRY_PYTHON2` env variable usage~~ (getsentry/sentry#22460) 2. ~~Switch getsentry/onpremise to Python 3 by default*, introducing the `SENTRY_PYTHON2` env var for Py2 builds via the `-py2` suffix~~ (#763) 3. ~~Move the unsuffixed version of the builds to Python 3~~ (getsentry/sentry#22466) 4. **Remove the `SENTRY_PYTHON3` env var support and `-py3` prefix usage from getsentry/onpremise** 5. Remove tagging of `-py3` builds from getsentry/sentry
BYK
added a commit
to getsentry/sentry
that referenced
this pull request
Dec 4, 2020
This is the final step in making the PY3 version the default for Docker images and self-hosted. It is part **5/5**: 1. ~~Add `-py2` variants for the Python 2 build tags and introduce the `SENTRY_PYTHON2` env variable usage~~ (#22460) 2. ~~Switch getsentry/onpremise to Python 3 by default*, introducing the `SENTRY_PYTHON2` env var for Py2 builds via the `-py2` suffix~~ (getsentry/self-hosted#763) 3. ~~Move the unsuffixed version of the builds to Python 3~~ (#22466) 4. ~~Remove the `SENTRY_PYTHON3` env var support and `-py3` prefix usage from getsentry/onpremise~~ (getsentry/self-hosted#764) 5. **Remove tagging of `-py3` builds from getsentry/sentry**
BYK
added a commit
that referenced
this pull request
Dec 4, 2020
This is in preparation to make the PY3 version the default for Docker images and self-hosted. It is part **4/5**: 1. ~~Add `-py2` variants for the Python 2 build tags and introduce the `SENTRY_PYTHON2` env variable usage~~ (getsentry/sentry#22460) 2. ~~Switch getsentry/onpremise to Python 3 by default*, introducing the `SENTRY_PYTHON2` env var for Py2 builds via the `-py2` suffix~~ (#763) 3. ~~Move the unsuffixed version of the builds to Python 3~~ (getsentry/sentry#22466) 4. **Remove the `SENTRY_PYTHON3` env var support and `-py3` prefix usage from getsentry/onpremise** 5. Remove tagging of `-py3` builds from getsentry/sentry
BYK
added a commit
to getsentry/sentry
that referenced
this pull request
Dec 4, 2020
This is the final step in making the PY3 version the default for Docker images and self-hosted. It is part **5/5**: 1. ~~Add `-py2` variants for the Python 2 build tags and introduce the `SENTRY_PYTHON2` env variable usage~~ (#22460) 2. ~~Switch getsentry/onpremise to Python 3 by default*, introducing the `SENTRY_PYTHON2` env var for Py2 builds via the `-py2` suffix~~ (getsentry/self-hosted#763) 3. ~~Move the unsuffixed version of the builds to Python 3~~ (#22466) 4. ~~Remove the `SENTRY_PYTHON3` env var support and `-py3` prefix usage from getsentry/onpremise~~ (getsentry/self-hosted#764) 5. **Remove tagging of `-py3` builds from getsentry/sentry**
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is in preparation to make the PY3 version the default* for Docker images and self-hosted. It is part 2/5:
Add(ci(py3): Make py2 builds available under-py2variants for the Python 2 build tags and introduce theSENTRY_PYTHON2env variable usage-py2suffix sentry#22460)SENTRY_PYTHON2env var for Py2 builds via the-py2suffixSENTRY_PYTHON3env var support and-py3prefix usage from getsentry/onpremise-py3builds from here* this will only happen when item 3 above gets landed