Generated python scripts fail to import correctly

[damienmg]

This is a direct consequence of http://bugs.python.org/issue6386:

$ bazel run  b:bin
INFO: Found 1 target...
Target //b:bin up-to-date:
  bazel-genfiles/b/__init__.py
  bazel-bin/b/bin
INFO: Elapsed time: 0.097s, Critical Path: 0.00s

INFO: Running command line: bazel-bin/b/bin
Traceback (most recent call last):
  File "/private/var/tmp/_bazel_dmarting/d13d2b815007acab3d9cf94b6c2cd8b9/tata/bazel-out/local_darwin-fastbuild/bin/b/bin.runfiles/b/__init__.py", line 1, in <module>
    import a
ImportError: No module named a
ERROR: Non-zero return code '1' from command: Process exited with status 1.
$ ls b
BUILD   a.py
$ cat b/BUILD 
genrule(
  name = "init",
  cmd = "echo 'import a' > $@",
  outs = ["__init__.py"],
)

py_binary(
  name = "bin",
  main = "__init__.py",
  srcs = ["__init__.py", "a.py"],
)
$ cat b/a.py 
print 'Hello, World!'
$ 

This should works.

[damienmg]

workaround is to do a from b import a as the pythonpath is set to the workspace root.

[damienmg]

fwiw, because of that bug, the .pyc files are generated in the workspace root if the main script is not generated and without sandboxing.

[sgowroji]

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.