cnsgsz

Thanks Derek for the update. What would be your recommendation for such a file system library? My use case is pretty simple: just something that would work both on gcs...

@groodt: Do you mean `python -m venv ...` and `pip install ...` the locked requirement files under that? @jvolkman I saw you created [rules_pyvenv](https://github.com/cedarai/rules_pyvenv). How does it relate or compare...

Entry scripts for py_binary targets seem to have directories of external packages (`python_imports`) and add them to PYTHONPATH. ``` python_imports = 'com_google_protobuf/python' python_path_entries = CreatePythonPathEntries(python_imports, module_space) python_path_entries += GetRepositoriesImports(module_space, True)...

> it'll install generated code (such as protocol buffers) in your venv so that you can use them in your IDE. Without `rules_pyvenv`, "go to definition" on a foo_pb2.py goes...

Is this issue resolved? I don't seem to find an implementation in the thread.

I also ran into the same issue. It shows up as `kfp.__version__` does not exist, as `kfp` points to the one under `kfp_pipeline_spec`. It seems incorrect to me that `kfp`...

@cristifalcas : do you know what changed? why don't you need the hack anymore? @chensun: I understand the difficulty in making it backward compatible etc, though I'm still not convinced...

I confirm that bazel added `pip_parsed_deps_kfp_pipeline_spec/site-packages/kfp/__init__.py` and removing it as @cristifalcas suggested works as a work-around. Nonetheless, this work-around does not seem to conform to [namespace packages' documentation](https://packaging.python.org/en/latest/guides/packaging-namespace-packages/), as `kfp_pipeline_spec`...