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

drop support for py37 #474

Merged
merged 2 commits into from
May 30, 2023
Merged

drop support for py37 #474

merged 2 commits into from
May 30, 2023

Conversation

mikealfare
Copy link
Contributor

resolves dbt-labs/dbt-core#7082

Description

Drop support for py37.

Checklist

@mikealfare mikealfare self-assigned this May 30, 2023
@cla-bot cla-bot bot added the cla:yes label May 30, 2023
@mikealfare mikealfare marked this pull request as ready for review May 30, 2023 21:24
@mikealfare mikealfare requested a review from a team as a code owner May 30, 2023 21:24
@nathaniel-may nathaniel-may merged commit 85c1d19 into main May 30, 2023
@nathaniel-may nathaniel-may deleted the feature/python/drop-py37 branch May 30, 2023 21:38
@github-actions
Copy link
Contributor

The backport to 1.5.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.5.latest 1.5.latest
# Navigate to the new working tree
cd .worktrees/backport-1.5.latest
# Create a new branch
git switch --create backport-474-to-1.5.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 85c1d199e8dd088b672e2157ae1f023c1a4b825c
# Push it to GitHub
git push --set-upstream origin backport-474-to-1.5.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.5.latest

Then, create a pull request where the base branch is 1.5.latest and the compare/head branch is backport-474-to-1.5.latest.

colin-rogers-dbt pushed a commit that referenced this pull request Jun 20, 2023
* drop support for py37

* drop support for py37

(cherry picked from commit 85c1d19)
@colin-rogers-dbt colin-rogers-dbt mentioned this pull request Jun 20, 2023
6 tasks
nathaniel-may pushed a commit that referenced this pull request Jun 20, 2023
* drop support for py37

* drop support for py37

(cherry picked from commit 85c1d19)

Co-authored-by: Mike Alfare <13974384+mikealfare@users.noreply.github.com>
@github-actions
Copy link
Contributor

The backport to 1.3.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.3.latest 1.3.latest
# Navigate to the new working tree
cd .worktrees/backport-1.3.latest
# Create a new branch
git switch --create backport-474-to-1.3.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 85c1d199e8dd088b672e2157ae1f023c1a4b825c
# Push it to GitHub
git push --set-upstream origin backport-474-to-1.3.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.3.latest

Then, create a pull request where the base branch is 1.3.latest and the compare/head branch is backport-474-to-1.3.latest.

@github-actions
Copy link
Contributor

The backport to 1.0.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.0.latest 1.0.latest
# Navigate to the new working tree
cd .worktrees/backport-1.0.latest
# Create a new branch
git switch --create backport-474-to-1.0.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 85c1d199e8dd088b672e2157ae1f023c1a4b825c
# Push it to GitHub
git push --set-upstream origin backport-474-to-1.0.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.0.latest

Then, create a pull request where the base branch is 1.0.latest and the compare/head branch is backport-474-to-1.0.latest.

@github-actions
Copy link
Contributor

The backport to 1.2.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.2.latest 1.2.latest
# Navigate to the new working tree
cd .worktrees/backport-1.2.latest
# Create a new branch
git switch --create backport-474-to-1.2.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 85c1d199e8dd088b672e2157ae1f023c1a4b825c
# Push it to GitHub
git push --set-upstream origin backport-474-to-1.2.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.2.latest

Then, create a pull request where the base branch is 1.2.latest and the compare/head branch is backport-474-to-1.2.latest.

@github-actions
Copy link
Contributor

The backport to 1.1.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.1.latest 1.1.latest
# Navigate to the new working tree
cd .worktrees/backport-1.1.latest
# Create a new branch
git switch --create backport-474-to-1.1.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 85c1d199e8dd088b672e2157ae1f023c1a4b825c
# Push it to GitHub
git push --set-upstream origin backport-474-to-1.1.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.1.latest

Then, create a pull request where the base branch is 1.1.latest and the compare/head branch is backport-474-to-1.1.latest.

@github-actions
Copy link
Contributor

The backport to 1.4.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.4.latest 1.4.latest
# Navigate to the new working tree
cd .worktrees/backport-1.4.latest
# Create a new branch
git switch --create backport-474-to-1.4.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 85c1d199e8dd088b672e2157ae1f023c1a4b825c
# Push it to GitHub
git push --set-upstream origin backport-474-to-1.4.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.4.latest

Then, create a pull request where the base branch is 1.4.latest and the compare/head branch is backport-474-to-1.4.latest.

mikealfare added a commit that referenced this pull request Jun 29, 2023
(cherry picked from commit 85c1d19)
mikealfare added a commit that referenced this pull request Jun 29, 2023
(cherry picked from commit 85c1d19)
mikealfare added a commit that referenced this pull request Jun 29, 2023
(cherry picked from commit 85c1d19)
mikealfare added a commit that referenced this pull request Jun 29, 2023
cherry picked from commit (85c1d19)
mikealfare added a commit that referenced this pull request Jun 29, 2023
(cherry picked from commit 85c1d19)
mikealfare added a commit that referenced this pull request Jun 29, 2023
(cherry picked from commit 85c1d19)
mikealfare added a commit that referenced this pull request Jun 29, 2023
mikealfare added a commit that referenced this pull request Jul 5, 2023
* drop support for py37 (#474)

(cherry picked from commit 85c1d19)

* fix comment

* fixed release branch
mikealfare added a commit that referenced this pull request Jul 5, 2023
* drop support for py37 (#474)

(cherry picked from commit 85c1d19)

* fix comment

* fixed release branch
mikealfare added a commit that referenced this pull request Jul 5, 2023
* drop support for py37 (#474)

cherry picked from commit (85c1d19)

* fix comment
mikealfare added a commit that referenced this pull request Jul 5, 2023
* drop support for py37 (#474)

(cherry picked from commit 85c1d19)

* Update CONTRIBUTING.MD

Co-authored-by: leahwicz <60146280+leahwicz@users.noreply.github.com>

* Update setup.py

Co-authored-by: leahwicz <60146280+leahwicz@users.noreply.github.com>

---------

Co-authored-by: leahwicz <60146280+leahwicz@users.noreply.github.com>
abbywh pushed a commit to abbywh/dbt-redshift that referenced this pull request Oct 11, 2023
* drop support for py37

* drop support for py37
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.

[CT-2228] Python 3.7 End of Life: June 2023
3 participants