Benjamin Peterson
Benjamin Peterson
> The underlying issue is that the runtime environment is hermetic but the setup environment is leaky - as far as I can tell, vpip is given access to system...
We use a `site.cfg` to point `scipy` to our copy of OpenBLAS. We avoid the hermeticity problem by building everything with a minimal sandbox root fs. https://github.com/bazelbuild/bazel/issues/6994#issuecomment-457438551
Thanks. I think it would make the most sense to only support Python 3. So, add `python2_compatible = False` where necessary.
We probably don't have the resources to do this, unfortunately.
Both, but it's mostly the thinking involved rather than the mechanics that's extra work. What will be the semantic meaning attached to a tag? As far as we're concerned, each...
We explicitly set it in our linker wrapper: https://github.com/dropbox/dbx_build_tools/blob/878fa997e7313c52692fd8d308660786a3442e59/build_tools/py/ldshared-wrapper.sh#L54
The principle here is that we always build shared modules for Python extensions. So, it makes sense that we ignore whatever Bazel's C++ rules think the linking configuration is. I'm...
It seems like the problem with `-shared` in default ldflags is when packages expect to build executables as part of their `setup.py`. For example, https://pypi.org/project/vmprof runs `./configure` from its `setup.py`.
This was fixed by https://github.com/protocolbuffers/protobuf/commit/887daf693fa17d7baf7b55b278132a7115beae30#diff-d0961d63325c9a3f30b4769cf5d53d663bcb10d545c1125e4e7ebbd80182a992R683.
Likely to be #4008.