witty-crayon-22786
03/28/2019, 4:12 PMfierce-park-88503
03/28/2019, 5:12 PMprovides
clause in the whole repo afaik, b) it seems like in that case the error would be AmbiguousOwnerError
, instead of NoOwnerError
witty-crayon-22786
03/28/2019, 5:13 PM./pants paths thing/I/want/a/wheel/for an/internal/python_library/target/I/depend:on
show you a path between them?fierce-park-88503
03/28/2019, 5:16 PM[thing/I/want/a/wheel/for , an/internal/python_library/target/I/depend:on]
it’s a direct depan/internal/python_library/target/I/depend:on
when trying to run setup-py on thing/I/want/a/wheel/for
?witty-crayon-22786
03/28/2019, 5:17 PMfierce-park-88503
03/28/2019, 5:17 PMwitty-crayon-22786
03/28/2019, 5:17 PMfierce-park-88503
03/28/2019, 5:18 PMthing/I/want/a/wheel/for
to be a parent in the directory/package hierarchy of an/internal/python_library/target/I/depend:on
. like the latter would actually have to be thing/I/want/a/wheel/for/an/internal/python_library/target/I/depend:on
. but I’m not sure I understand exactly what’s going onwitty-crayon-22786
03/28/2019, 5:19 PMfierce-park-88503
03/28/2019, 5:20 PMdependencies
. now the wheel builds, but none of the code ends up actually making it into the wheel? like the wheel just consists of a single __init__.py
filesetup-py
goal should include code from transitive deps, not just the direct dep of the python_library that’s being `setup-py`d, right?witty-crayon-22786
03/29/2019, 9:54 PM