You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, any data files or scripts included in a wheel are exposed to Bazel directly from the fully-qualified source workspace (e.g. @pip__lxml_4_3_3_cp36_cp36m_manylinux1_x86_64//data/somedir:foo), but this label is long and cumbersome, requires the developer to add their own select statements in order to support multi-platform, and would have to be modified whenever the requirement is updated since it includes the version.
Ideally, this should be available via an alias just like the py_library (e.g. @pip//lxml:data/somedir/foo).
The text was updated successfully, but these errors were encountered:
…lar distribution
Each distro package under the @pip repo now contains a `repos.bzl` file with variables
for conveniently accessing the label of each source repo. This can be used for more
easily accessing data files.
Resolves#29
Currently, any data files or scripts included in a wheel are exposed to Bazel directly from the fully-qualified source workspace (e.g.
@pip__lxml_4_3_3_cp36_cp36m_manylinux1_x86_64//data/somedir:foo
), but this label is long and cumbersome, requires the developer to add their ownselect
statements in order to support multi-platform, and would have to be modified whenever the requirement is updated since it includes the version.Ideally, this should be available via an alias just like the
py_library
(e.g.@pip//lxml:data/somedir/foo
).The text was updated successfully, but these errors were encountered: