-
Notifications
You must be signed in to change notification settings - Fork 74k
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
Repository '@python' is not defined #66203
Comments
@nmdesai22, |
Then , give below command to buiild project
I get below Log on the terminal
|
Update - As a Temporary fix, I added python definitions in my Project's {project}/WORKSPACE file, and it worked. and Project can be build succesfully I added below additional changes in WORKSPACE.
|
@nmdesai22, If it still does not work, please try to follow the steps below Click to expand!Step1: Install Python 3.10 in C:\Step2: Create and activate Virtual env Step3: git clone https://github.com/tensorflow/tensorflow.git==>(venv39_new) D:\user\tensorflow> Step4: Set up all the paths and files set BAZEL_SH=C:\msys64\usr\bin\bash.exe set BAZEL_VS=C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools set BAZEL_VC=C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC set PATH=c:\Tools\Bazel;D:\user\venv39_new\Scripts;C:\Program Files\Python39\Scripts\ set PYTHON_BIN_PATH=D:/user/venv39_new/Scripts/python.exe Thank you! |
I am using Linux ENV to build the project. I did try all three suggestions, but get the same error |
Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
2.16.1
Custom code
Yes
OS platform and distribution
Linux Ubuntu 22.04.1
Mobile device
No response
Python version
3.10.12
Bazel version
5.4.1
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
while building a tool with tensorflow v2.16.1, it gives build error as "The repository '@python' could not be resolved: Repository '@python' is not defined."
Standalone code to reproduce the issue
Relevant log output
The text was updated successfully, but these errors were encountered: