-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Bigquery: import error with v.1.23.0 #9965
Comments
I can reproduce the same behavior |
My pipeline broke today. I install
So i've migrated to previous version(1.22.0) and it's working fine. |
@smdmts @shihabuddinbuet @SaschaHeyer Please update or install the latest version of |
@HemangChothani |
@SaschaHeyer |
Can reproduce the same |
Adding |
Please verify via python -m pip freeze that this python environment has up to date packages. In a clean environment this seems to work.
And the imports work as expected.
|
feel free to reopen if this wouldn't solve the problem. |
Hi, Would it be possible for either The problem is that I agree that this problem can be fixed by manually upgrading |
Sorry that you have encountered this issue. I should have checked the minimum version of Indeed, the correct fix is for bigquery to add |
|
I'm still facing this issue with the updated package. google-cloud-bigquery==1.22.0 works fine. I'm using the google-cloud-bigquery==1.23.1 and six==1.13.0 package in a jupyter notebooks environment. https://pypi.org/project/google-cloud-bigquery/1.23.1/ Code example: Stacktrace:
|
@shounakG I'm sorry that you're still experiencing this issue. Can you run
from the Jupyter notebook to double-check the package versions installed in the kernel? |
Hi @tswast thanks for getting back! I did check pip freeze and it showed the latest version (1.23.1), but still gave out the same error. In the jupyter notebooks environment however, a restart of kernel was needed for changes to take effect. It worked flawlessly after a kernel restart. Thanks for the help! |
I'm having this issue and can't seem to figure out what the deal is. I got around this by manually editing the schema.py file to include the following:
This is driving me nuts Python 3.7.5 |
@jordangonzales Latest version of google.cloud.bigquery package is 1.23.1. Try downgrading it to 1.23.0 as it's working with six==1.14 |
had the same issue with 1.24.0, using 1.23.0 instead fixed it |
Why is this issue closed? |
@SaschaHeyer I have tried to reproduce the issue but not able to do that, Could please share your environment details? My Environment:
|
I'm also facing the same error here |
I am reproducing this issue with these versions: |
I'm also facing the same error here |
i am facing the same error 😭 |
To all people still facing the trouble - this issue lives in the old repository, which is why it probably did not receive enough attention lately, sorry for that. I suggest continuing the thread under the new issue @sagydr created. Please also double check that |
Still facing this issue. My jenkins deployment pipeline broke with the same message. Packages on my server:
Please advice. |
This works for me, thank you! |
Same issue here. Did you solve it? |
The same problem here. |
@JoshuaCrestone six==1.15.0 works? |
@aoliu95 - this fixed it for me. I am using Bazel to build a python project with python rules from https://github.com/dillon-giacoppo/rules_python_external. Even though my six dependency was at 1.15.0, when running my tests, the version would show as 1.12.0. It turned out, 1.12.0 was a hard dependency of the protobuf Bazel rules I was importing. Perhaps it could have been fixed by changing WORKSPACE rule ordering to get the whl dependency to override the protobuf dependency? |
@JoshuaCrestone It seems the issue persists even I upgrade my six to 1.15.0
Which version are you using for |
@aoliu95 - are you using Bazel? In my case, I am using Bazel, and a workspace dependency was overwriting a project dependency. If you add:
to the failing code, you will see which version of six is being resolved at runtime. For me, my requirements.txt specified six 1.15.0, but at runtime, it was resolving to 1.12.0, and this conflict was coming from my WORKSPACE dependency on protobuf. P.S. google-cloud-bigquery==1.28.0, google-api-python-client==1.12.3 |
I solved the issue at googleapis/python-bigquery-pandas#304 (comment). It was because my Jupyter was not picking the newly installed six after running |
google-cloud-bigquery==1.24.0 six==1.14 works with python 2.7 but not python 3.7 |
I am also getting this same error message with google-cloud-storage==1.33.0 and six==1.15.0. I have other dependencies that require Python 3.7, did anyone find a solution that works with 3.7? |
Steps to reproduce
Code example
Stack trace
The text was updated successfully, but these errors were encountered: