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
TF2 Nightly-20190607 broken import #29536
Comments
Sorry about that, I'll fix today |
This is now fixed, I have 3 more other issues caused by the virtual pip that needs fixing but I'll keep an eye. Please let me know if this still doesn't work. |
Summary: Due to <tensorflow/tensorflow#29536>. This unblocks our CI until tomorrow’s nightlies are pushed. Test Plan: Fingers crossed. wchargin-branch: pin-20190606-nightly
Summary: Due to <tensorflow/tensorflow#29536>. This unblocks our CI until tomorrow’s nightlies are pushed. Test Plan: Fingers crossed. wchargin-branch: pin-20190606-nightly
Hello I am getting this issue from TF 2.0 in Google Colab. The code was running previously, but all of a sudden, it started outputting this error as shown below. AttributeError Traceback (most recent call last) /usr/local/lib/python3.6/dist-packages/tensorflow/init.py in () AttributeError: module 'tensorflow_core' has no attribute 'compiler' |
Hi @EziamaUgonna, install yesterday's nightly with |
This fix is required as the API generation job doesn't check that `__all__` has been initialized to contain the `core`, `compiler` and `python` symbols just a little before these symbols are deleted. As a result, when someone does `from tensorflow import *`, the interpreter sees these symbols in `tensorflow.__all__` and tries to bring them up in scope. However, as they are deleted this fails. 5a93bb solved this issue for V1 API and the issue surfaced for V2 API with f1ffa02, the virtual pip package change. PiperOrigin-RevId: 252060393
System information
Describe the current behavior
TF2 nightly breaks with this error:
Code to reproduce the issue
Other info / logs
Probably related to the commit mentioned in #29532 but not positive.
The text was updated successfully, but these errors were encountered: