-
Notifications
You must be signed in to change notification settings - Fork 563
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
pip_import doesn't work with tensorflow #71
Comments
I can confirm. The tensorflow module is completely missing a
|
+1, is there any progress on this issue? |
+1 |
1 similar comment
+1 |
Note that this is due to issue #92 . There's a workaround posted there for TensorFlow. |
See https://groups.google.com/d/msg/bazel-sig-python/iQjV9sfSufw/qRtG3toDBAAJ -- short version: expect improvements to our Python rules in August. |
Any movement on this? :) |
Hi Justin, the movement is that I've taken over maintenance on Python-related issues, including rules_python, though I'm still getting a handle on priorities. Is this issue a regression or was it always broken? |
I'm pretty sure the root cause (#92) has always existed. |
It doesn't seem to have ever worked and it's kinda ironic that what is probably the most popular Bazel project can't be imported from another one through pip. Kinda steers you toward building it through Bazel. Not bad to increase adoption. (That's a silly joke, to be clear.) |
To add more detail: we use TF both by using pip and compiling sources through a nested workspace, so we get to enjoy the worst of both worlds, when it comes to bugs. This issue is our worst pip headache, along with #96 (packages are fetched eagerly when first starting Bazel, rather than lazily when first using them). |
+1 |
Yeah, I've just now run into this, too. Running a fork of rules_python to fix this doesn't seem like a great workaround |
(I came to this after giving up on depending on tensorflow as a normal bazel extension, of course. They have that wild user-interaction-required ./configure script you seem to have to run that does a bunch of heuristics on your local filesystem to generate its own bazelrc file. Not great!) |
I tried to get tensorflow to load with anaconda and conda. No success with Windows 10, using python 3.6 and 3.5. Any workaround for Windows without using Linux or Microsoft VS 20XX would be appreciated. https://anaconda.org was not of any use I could find. PackagesNotFoundError: The following packages are not available from current channels:
Current channels:
To search for alternate channels that may provide the conda package you're
and use the search bar at the top of the page. |
Just wanted a heads up on whether the No module issue here similar to my issue here: #214 |
try our implementation here https://github.com/ali5h/rules_pip |
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format>
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format> [Exported from 6e9120c2a18494ae23099965a1a882da046d2c59]
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format> [Exported from 6e9120c2a18494ae23099965a1a882da046d2c59]
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format> [Exported from 6e9120c2a18494ae23099965a1a882da046d2c59]
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format> [Exported from 6e9120c2a18494ae23099965a1a882da046d2c59]
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format> [Exported from 6e9120c2a18494ae23099965a1a882da046d2c59]
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format>
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format>
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format>
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format>
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format>
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format>
This is to workaround a known issue with packaging Tensorflow as a pip dependency in bazel. See: github.com/bazelbuild/rules_python/issues/71 Signed-off-by: format 2020.01.12 <github.com/ChrisCummins/format>
+1, any updates? |
We're working on incorporating the packaging code from |
rules_python 0.1.0 has been released which upstreams the rules_python_external repo. Please switch from |
WORKSPACE
requirements.txt
BUILD
test.py
Raises:
ImportError: 'No module named tensorflow'
The text was updated successfully, but these errors were encountered: