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

[Feature] Spike on supporting Py3.12 in dbt-postgres #17

Closed
3 tasks done
colin-rogers-dbt opened this issue Feb 14, 2024 · 0 comments · Fixed by #135
Closed
3 tasks done

[Feature] Spike on supporting Py3.12 in dbt-postgres #17

colin-rogers-dbt opened this issue Feb 14, 2024 · 0 comments · Fixed by #135
Assignees
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-postgres functionality, rather than a Big Idea better suited to a discussion

Describe the feature

We need to try upgrading to py312 and either it works with minimal changes or scope out what needs to happen to make it work

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 the enhancement New feature or request label Feb 14, 2024
@colin-rogers-dbt colin-rogers-dbt changed the title [Feature] Spike on supporting Py3.12 [Feature] Spike on supporting Py3.12 in dbt-postgres Jul 3, 2024
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.

3 participants