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

[CT-1637] [Feature] Handle py311-related changes in dbt-core #542

Closed
3 tasks done
colin-rogers-dbt opened this issue Dec 9, 2022 · 0 comments · Fixed by #543
Closed
3 tasks done

[CT-1637] [Feature] Handle py311-related changes in dbt-core #542

colin-rogers-dbt opened this issue Dec 9, 2022 · 0 comments · Fixed by #543
Labels
enhancement New feature or request

Comments

@colin-rogers-dbt
Copy link
Contributor

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt-spark functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Downstream changes needed due to dbt-core changes to support python 3.11

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

@colin-rogers-dbt colin-rogers-dbt added enhancement New feature or request triage labels Dec 9, 2022
@github-actions github-actions bot changed the title [Feature] Support Py 3.11 Core changes [CT-1637] [Feature] Support Py 3.11 Core changes Dec 9, 2022
@jtcohen6 jtcohen6 changed the title [CT-1637] [Feature] Support Py 3.11 Core changes [CT-1637] [Feature] Handle py311-related changes in dbt-core Dec 12, 2022
@jtcohen6 jtcohen6 removed the triage label Dec 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants