-
Notifications
You must be signed in to change notification settings - Fork 79
Incompatibility with Python 3.7 #711
Comments
I'm also getting this issue. So far by replacing references to async in __init__.py, _async.py and _lambda_job.py to asynchron I've managed to get it to import. I have yet to determine if this will cause any issues down the line. |
@QuinRiva Could you provide more details? I've replaced all references to async in the modules you listed and I still get this error: |
Sorry, it looks like the issues are somewhat more extensive. I would be good to determine if this is a live project, as currently many of the dependencies are wildly outdated - in thus incompatible with many of Google's other libraries. |
I'm also facing the same problem. :( |
same problem here. |
from datalab import storage as storage |
I got error when using python3.7 from google import datalab any body still have same problem ? |
Using google-cloud-bigquery because datalab in python3.7 yields syntax error (see googledatalab/pydatalab#711)
* Fix jupytext notebook load error. * Update jupytext version in all the notebooks * Set notebook interpreter to python3.7 * Update start.sh and README * Remove incompatible notebook deps functools32 and futures * Replace google.datalab with google.cloud for bigquery in notebooks * Using google-cloud-bigquery because datalab in python3.7 yields syntax error (see googledatalab/pydatalab#711) [ci skip]
* Fix jupytext notebook load error. * Update jupytext version in all the notebooks * Set notebook interpreter to python3.7 * Update start.sh and README * Remove incompatible notebook deps functools32 and futures * Replace google.datalab with google.cloud for bigquery in notebooks * Using google-cloud-bigquery because datalab in python3.7 yields syntax error (see googledatalab/pydatalab#711) [ci skip]
Bug:
Importing the datalab module fails in python 3.7
Steps to Reproduce:
Expected:
Successful import
Stack Trace:
Notes:
Previous versions of python successfully imported datalab, so I'm assuming it's caused by async being a keyword in Python 3.7 hence the syntax error.
The text was updated successfully, but these errors were encountered: