-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Broken DBT 18 update on Brew ... DBT doesn't support Python 3.9 #2865
Comments
It's possible that hologram version doesn't support Python 3.9. There were some changes in a recent hologram commit to support 3.9, but it hasn't been packaged yet and dbt support for 3.9 hasn't been done yet. |
Thanks, you're right. Resolved via instructions in this thread to use |
Experimenting the same bug inside a GitHub Action (python 3.9).
|
There are broken dependencies on the DBT brew installation for Python 3.9. Instead use
|
I am using Conda and this is what I did to resolve this issue. Downgrade python from 3.9 to 3.8:
Do a force reinstall of dbt:
Run
|
This bug hasn't been solved, please reopen the ticket. Here is the GitHub action workflow file running Python < 3.9 runs-on: ubuntu-latest
strategy:
matrix:
python-version: [ '3.6', '3.8' ]
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Setup Python
uses: actions/setup-python@v2.1.4
- name: Setup dbt
run: |
python3 -m venv dbt-env
source dbt-env/bin/activate
pip3 install dbt
dbt --version |
The latest version of dbt (v0.18.1) does not support python 3.9. We plan to add py39 support (#2822) for the next release of dbt (v0.19.0). If it proves straightforward, I'd also like to release a patch version (v0.18.2) that is compatible with python 3.9 as well. In the meantime, I am going to close this issue as a duplicate of #2822. |
Hello, I still have this issue with sqlfluff, dbt 0.19 and python 3.9 pip3 --version When running sqlfluff lint with |
Hey @Startouf, I'm not positive if that clarifies the jinja issue you're seeing, but suffice to say, it is expected that |
confirmed this works in a clean py39 env
|
Still encountering this issue for 0.19.1 with a fresh dbt install on Arch Linux and python 3.9. Creating a virtualenv with 3.7 fixed it for me. |
thanks! this works for me 👍🏽 was trying to install dbt 0.18.0 |
Describe the bug
This issue originally started when I merged a change into production to begin using the Shopify DBT package. The merge broke because our prod machine was still on dbt 17. So when I went to upgrade I hit the below issues.
Currently, I get the below stack trace when running
dbt --version
while trying to upgrade to dbt 18.1. I imagine this has something to do with my brew/python setup environment but am not quite sure exactly how to debug after about a day of brute forcing various solutions. Thanks for your help.Steps To Reproduce
dbt --version
Expected behavior
dbt --version
to return the updated versionSystem information
Which database are you using dbt with?
The output of
dbt --version
:The operating system you're using:
Ubuntu 18.04.5 LTS (GNU/Linux 5.4.0-1028-aws x86_64)
The output of
python --version
:Python 3.9.0 (I do have multiple installs of python which may be influencing the issue)
Additional context
My best assumption is the issue lies here with the billion python installs, but not sure.
Thank you so much
The text was updated successfully, but these errors were encountered: